AI agents call trend_gsc to retrieve information from Geoseo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Google Search Console (GSC) data to analyze trends over time. It retrieves and presents analytics data (clicks, impressions, ranking positions) from stored snapshots. There is no creation, modification, deletion, code execution, or financial transaction involved. This is a straightforward data retrieval operation with no side effects, fitting the Read category.
From the tool's definition Tool provides 'Time-series of clicks/impressions/position from stored GSC snapshots' — retrieving historical search performance metrics without modification or side effects.
Attacks that exploit this kind of access
Time-series of clicks/impressions/position from stored GSC snapshots. It is categorised as a Read tool in the Geoseo MCP Server, which means it retrieves data without modifying state.
Register the Geoseo MCP server in PolicyLayer and add a rule for trend_gsc: 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 Geoseo. Nothing to install.
trend_gsc 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 trend_gsc 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 trend_gsc. 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.
trend_gsc is provided by the Geoseo MCP server (rachit8484/geoseo-mcp). 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 →