open-seo-mcp-skills

Security Hardening Guide: open-seo-mcp-skills

Least-privilege permissions

• Use a dedicated Google account for this MCP with only GSC (Google Search Console), GA4 (Google Analytics), and Ads access—not your main business account. If the account is compromised, damage stays limited.
• Review OAuth scopes before connecting: When prompted to grant access, verify Ryze only requests "read" permissions for reports and data, never "write" or "delete" for campaigns or budgets. Revoke access immediately if it asks for broader rights.
• Rotate credentials quarterly: Regenerate API keys and revoke old tokens in Google Cloud Console to limit exposure if they're accidentally leaked.
• Disable unused integrations: Only connect GSC, GA4, or Ads if you actually need them; don't authorize all three if you only track rankings.

Network isolation

• Run on a separate device or isolated network if handling competitor or highly sensitive client data; don't use the same machine for public web browsing or email.
• Use a VPN when accessing the MCP to encrypt traffic between your device and connector.get-ryze.ai, especially on public WiFi.
• Don't share the MCP connection URL or API credentials via email, Slack, or chat—treat them like passwords.

Monitoring

• Check Google's "Connected apps & sites" (myaccount.google.com/permissions) monthly; look for Ryze and revoke if you stop using it.
• Review Claude conversation history: Export or delete chats containing sensitive campaign data, bidding strategies, or competitor insights after use (Anthropic may retain training data otherwise).
• Set up alerts in Google Analytics and Ads for unusual activity—sudden budget changes, new keywords, or account access from unknown locations.

Red flags to watch for

• Unexpected permission requests: If the MCP suddenly asks to "write" to Ads or modify campaigns, stop and contact Ryze support immediately.
• Data slowness or failures: If the connector frequently times out or returns incomplete reports, don't assume it's safe—it could be under attack or leaking data silently.
• Ryze security incidents: Monitor Ryze's status page and GitHub for breaches; this tool has minimal community adoption (near-zero npm usage), so security patches may be slow.
• Claude leaking campaign details: If Claude-generated reports accidentally include exact bid amounts, budgets, or client names in public chats, treat it as a breach and rotate credentials.