data_delete

Delete a record by id.

SERVERYaver SOURCEyaver-cli

Critical RISK CLASS

Category Destructive

Parameters 32 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/data-delete.md

WHAT IT DOES

What data_delete does on Yaver

AI agents call data_delete to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required
`id`	string	Yes
`table`	string	Yes
`directory`	string	—

Parameters from the server's own tool schema.

RISK

Why data_delete is rated Critical

This tool irreversibly removes a record from storage. Deletion by ID is a classic destructive operation with no indication of soft-delete or reversibility. Misuse by an AI agent could result in permanent data loss, warranting high severity.

From the tool's definition "Delete a record by id" — explicitly deletes data identified by an ID

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs data_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For data_delete, this is the rule to start with:

data_delete Hidden

data_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "data_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every data_delete call is checked against it from then on.

FAQ

Questions about data_delete

What does the data_delete tool do? +

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

What parameters does data_delete accept? +

data_delete accepts 3 parameters: id, table, directory. Required: id, table. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on data_delete? +

Register the Yaver MCP server in PolicyLayer and add a rule for data_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 Yaver. Nothing to install.

What risk level is data_delete? +

data_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 data_delete? +

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

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

data_delete is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →