Delete a single keyword from a project.
AI agents call delete_keyword 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.
This tool irreversibly removes data (a keyword) from a project's configuration. While the blast radius is limited to a single keyword entry rather than an entire project or system, the action cannot be undone and represents data loss. Destructive is the appropriate category as it involves deletion of configured data.
From the tool's definition Tool name is 'delete_keyword' and description states it will 'Delete a single keyword from a project.' The verb 'delete' combined with the irreversible nature of removing a keyword from a project configuration makes this a destructive action.
Attacks that exploit this kind of access
Delete a single keyword 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_keyword: 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_keyword 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_keyword 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_keyword. 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_keyword 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 →