AI agents call search_console_sitemaps to retrieve information from Access 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 to retrieve sitemap metadata and status information. It is informational only, returns existing data without modifying state, and poses minimal risk even if misused by an agent (worst case: unnecessary API quota consumption). Classification as Read is appropriate.
From the tool's definition Tool description explicitly states 'List all submitted sitemaps' and 'verify sitemap indexing health' — pure retrieval operations with no modification or side effects. No mention of creating, modifying, deleting, or executing actions.
Attacks that exploit this kind of access
List all submitted sitemaps for a Google Search Console property, including their status and error counts. Use this to verify sitemap indexing health. It is categorised as a Read tool in the Access MCP Server, which means it retrieves data without modifying state.
Register the Access MCP server in PolicyLayer and add a rule for search_console_sitemaps: 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 Access. Nothing to install.
search_console_sitemaps 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 search_console_sitemaps 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 search_console_sitemaps. 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.
search_console_sitemaps is provided by the Access MCP server (scottpedia0/access). 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 →