Get crawl analytics — bot visits, top pages, status codes. Returns aggregated data for the specified time window.
AI agents call seo_crawl_stats to retrieve information from Inkwell MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports on existing SEO crawl statistics (bot visits, top pages, status codes). It is a read-only query operation that returns aggregated analytics data. There are no side effects, no data modification, no code execution, and no irreversible actions. The lowest risk category (Read) is appropriate.
From the tool's definition Tool description states 'Get crawl analytics' and 'Returns aggregated data' — retrieves and queries existing analytics data without modification or execution of external operations.
Attacks that exploit this kind of access
Get crawl analytics — bot visits, top pages, status codes. Returns aggregated data for the specified time window. It is categorised as a Read tool in the Inkwell MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Inkwell MCP Server MCP server in PolicyLayer and add a rule for seo_crawl_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 Inkwell MCP Server. Nothing to install.
seo_crawl_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 seo_crawl_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 seo_crawl_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.
seo_crawl_stats is provided by the Inkwell MCP Server MCP server (mumega-com/inkwell). 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 →