Delete a key-value pair within a transaction
AI agents call tx_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.
This tool permanently removes data from the KevoDB database. Although it operates within a transaction (which could theoretically be rolled back via rollback_transaction), the fundamental operation is destructive—it irreversibly deletes a key-value pair. In the context of an AI agent misusing this tool, it could cause permanent data loss if the transaction is committed.
From the tool's definition Tool name is 'tx_delete' and description states 'Delete a key-value pair within a transaction'. The verb 'Delete' and explicit mention of removing a key-value pair indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a key-value pair within a transaction. 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 tx_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.
tx_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 tx_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 tx_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.
tx_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 →