AI agents call seoagent_gsc_queries to retrieve information from Seoagent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns analytics data from Google Search Console about which search queries are driving traffic to a website. It performs read-only access to existing metrics and historical data with no side effects, no data modification, and no capability to alter or delete information. The blast radius of misuse is minimal - an attacker could only exfiltrate SEO analytics data already accessible through GSC.
From the tool's definition Tool retrieves 'top search queries' from Google Search Console - a pure data retrieval operation with no modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
Get top search queries driving traffic from Google Search Console. It is categorised as a Read tool in the Seoagent MCP Server, which means it retrieves data without modifying state.
Register the Seoagent MCP server in PolicyLayer and add a rule for seoagent_gsc_queries: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Seoagent. Nothing to install.
seoagent_gsc_queries is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the seoagent_gsc_queries rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for seoagent_gsc_queries. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
seoagent_gsc_queries is provided by the Seoagent MCP server (yagomp/seoagent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →