Critical Risk →

crud_delete

Delete a record

How to control crud_delete ↓

What crud_delete does on OODA Computer Control

AI agents call crud_delete to permanently remove resources in OODA Computer Control — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why crud_delete needs a policy

Destructive category is assigned because the tool performs deletion—an irreversible operation. While 'record' could theoretically refer to database records or file system entries, either interpretation represents data loss that cannot be recovered through normal means.

From the tool's definition Tool name 'crud_delete' combined with description 'Delete a record' indicates irreversible deletion of data.

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

How to control crud_delete

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

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

crud_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 OODA Computer Control — 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.

Related tools and policies

Go deeper

Questions about crud_delete

What does the crud_delete tool do? +

Delete a record. It is categorised as a Destructive tool in the OODA Computer Control 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 crud_delete? +

Register the OODA Computer Control MCP server in PolicyLayer and add a rule for crud_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 OODA Computer Control. Nothing to install.

What risk level is crud_delete? +

crud_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 crud_delete? +

Yes. Add a rate_limit block to the crud_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 crud_delete completely? +

Set action: deny in the PolicyLayer policy for crud_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 crud_delete? +

crud_delete is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OODA Computer Control tool call.

Start from OODA Computer Control, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ 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.