Critical Risk →

delete

Delete a specific record by ID.

How to control delete ↓

AI agents call delete to permanently remove resources in SurrealDB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool performs an irreversible deletion operation on database records. Even though it targets a specific record by ID (limiting blast radius compared to batch deletes), deletion is a destructive action that cannot be reverted. This places it in the Destructive category rather than Write.

From the tool's definition Tool name 'delete' combined with description 'Delete a specific record by ID' indicates irreversible removal of data. The action cannot be undone and permanently removes records from the database.

Documented attack patterns abuse exactly the kind of access delete gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and SurrealDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete"
  ]
}

delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register SurrealDB MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete tool do? +

Delete a specific record by ID. It is categorised as a Destructive tool in the SurrealDB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete? +

Register the SurrealDB 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 SurrealDB MCP Server. Nothing to install.

What risk level is delete? +

delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete? +

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.

How do I block delete completely? +

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.

What MCP server provides delete? +

delete is provided by the SurrealDB MCP Server MCP server (nsxdavid/surrealdb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SurrealDB MCP Server tool call.

Deterministic rules across all 10 SurrealDB MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

10 SurrealDB MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.