Delete a key-value pair from KevoDB
AI agents call delete to permanently remove resources in KevoDB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The delete operation permanently removes a key-value pair, which cannot be undone. This is an irreversible data loss operation, making it Destructive rather than Write. In the context of an AI agent with database access, an accidental or malicious deletion could result in permanent data loss.
From the tool's definition Tool name is 'delete' with description 'Delete a key-value pair from KevoDB' — this irreversibly removes data from the database.
Attacks that exploit this kind of access
Delete a key-value pair from KevoDB. It is categorised as a Destructive tool in the KevoDB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the KevoDB MCP Server MCP server in PolicyLayer and add a rule for 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 KevoDB MCP Server. Nothing to install.
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 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 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.
delete is provided by the KevoDB MCP Server MCP server (kevodb/kevo-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 →