write_delete_dataset_item

⚠️ DESTRUCTIVE: Permanently delete a dataset item. This write operation cannot be undone.

Server Langfuse MCP Server therealsachin/langfuse-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What write_delete_dataset_item does on Langfuse MCP Server

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

Why write_delete_dataset_item needs a policy

This tool irreversibly deletes data from a dataset, which is the defining characteristic of the Destructive category. The high severity reflects that an AI agent could accidentally or maliciously purge important dataset items without recovery. Confidence is high due to explicit 'DESTRUCTIVE' warning and clear permanent deletion semantics.

From the tool's definition Tool name includes 'delete'; description explicitly states '⚠️ DESTRUCTIVE: Permanently delete a dataset item. This write operation cannot be undone.' The keyword 'Permanently' and 'cannot be undone' clearly indicate irreversible data deletion.

Questions about write_delete_dataset_item

What does the write_delete_dataset_item tool do? +

⚠️ DESTRUCTIVE: Permanently delete a dataset item. This write operation cannot be undone. It is categorised as a Destructive tool in the Langfuse 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 write_delete_dataset_item? +

Register the Langfuse MCP Server MCP server in PolicyLayer and add a rule for write_delete_dataset_item: 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 Langfuse MCP Server. Nothing to install.

What risk level is write_delete_dataset_item? +

write_delete_dataset_item 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 write_delete_dataset_item? +

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

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

write_delete_dataset_item is provided by the Langfuse MCP Server MCP server (therealsachin/langfuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.