AI agents call bing_query_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.
This tool retrieves historical query performance statistics from Bing Webmaster Tools. It performs a data query operation with no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an attacker could only view the site owner's analytics data, which is a confidentiality concern but not operationally damaging.
From the tool's definition Tool name 'bing_query_stats' and description 'Last-6-months query stats from Bing Webmaster (clicks, impressions, position)' indicate retrieval of analytics data with no modification, deletion, or execution.
Attacks that exploit this kind of access
Last-6-months query stats from Bing Webmaster (clicks, impressions, position). 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 bing_query_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.
bing_query_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 bing_query_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 bing_query_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.
bing_query_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 →