Return Google Search Console snapshot data from DB_MARKETING.
AI agents call get_seo_data 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 queries and retrieves existing SEO analytics data from a database. There are no side effects, no data creation or modification, no code execution, and no irreversible operations. The blast radius of misuse is minimal—an agent could access analytics data it shouldn't see, but cannot alter systems or cause damage. This is a straightforward Read operation.
From the tool's definition Tool name 'get_seo_data' and description 'Return Google Search Console snapshot data from DB_MARKETING' indicate data retrieval without modification or execution. The verb 'Return' and lack of any mutation language confirm read-only operations.
Attacks that exploit this kind of access
Return Google Search Console snapshot data from DB_MARKETING. 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 get_seo_data: 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.
get_seo_data 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 get_seo_data 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 get_seo_data. 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.
get_seo_data 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 →