Remove a competitor from a project.
AI agents call delete_competitor to permanently remove resources in SurfRank MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a competitor from a project is a destructive action that removes tracked data. While the blast radius is limited (only affects one competitor record within a project), it is likely irreversible without re-adding the competitor manually, placing it in the Destructive category. Severity is medium because it affects a single project's competitor tracking rather than wiping entire projects or datasets.
From the tool's definition 'Remove a competitor from a project' — the word 'remove' (and the tool name 'delete_competitor') indicates an irreversible deletion of a competitor entry from a project.
Attacks that exploit this kind of access
Remove a competitor from a project. It is categorised as a Destructive tool in the SurfRank MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SurfRank MCP Server MCP server in PolicyLayer and add a rule for delete_competitor: 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 SurfRank MCP Server. Nothing to install.
delete_competitor 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 delete_competitor 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 delete_competitor. 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.
delete_competitor is provided by the SurfRank MCP Server MCP server (surfrankai/mcp-server). 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 →