AI agents call trend_stats 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.
The tool retrieves and queries metadata about stored data (row counts, sites, domains, snapshot timestamps) with no side effects. This is characteristic of Read category tools like 'list' and 'get' operations. There is no indication of data modification, deletion, external command execution, or financial operations.
From the tool's definition Tool description states it provides 'Inventory of what's stored: row counts, sites/domains, oldest/newest snapshots' — purely informational queries about stored data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Inventory of what's stored: row counts, sites/domains, oldest/newest 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_stats: 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_stats 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_stats 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_stats. 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_stats 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 →