AI agents call seoagent_gsc_pages 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 retrieves performance metrics from Google Search Console without creating, modifying, deleting, or executing operations. It is a straightforward data retrieval operation with no side effects, fitting the Read category with low severity since misuse would only expose existing SEO performance data already visible to the authenticated account holder.
From the tool's definition Tool retrieves data from Google Search Console ("Get top performing pages") with no mention of modification, deletion, or execution. The operation is explicitly a query sorted by metrics ("sorted by clicks or impressions").
Attacks that exploit this kind of access
Get top performing pages from Google Search Console, sorted by clicks or impressions. 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_pages: 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_pages 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_pages 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_pages. 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_pages 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 →