Delete a SERP job by id (cleanup).
AI agents call georanker_serp_delete to permanently remove resources in GeoRanker MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently deletes SERP (Search Engine Results Page) job records, which cannot be undone. This is a destructive operation that removes tracked SEO data. While the blast radius is somewhat mitigated by the fact that new jobs can be recreated, an agent with misconfigured parameters could accidentally delete important historical rank tracking data.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a SERP job by id (cleanup)', which indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a SERP job by id (cleanup). It is categorised as a Destructive tool in the GeoRanker MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GeoRanker MCP Server MCP server in PolicyLayer and add a rule for georanker_serp_delete: 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 GeoRanker MCP Server. Nothing to install.
georanker_serp_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the georanker_serp_delete 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 georanker_serp_delete. 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.
georanker_serp_delete is provided by the GeoRanker MCP Server MCP server (lucas111112/georanker-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 →