Delete a dataset and all its items.
AI agents call delete_dataset to permanently remove resources in Langfuse Mcp Python — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data without the possibility of reversal. Deleting a dataset and all its associated items is a destructive action that could result in significant data loss if invoked inappropriately by an AI agent. The blast radius includes loss of all historical data, annotations, and dependent items within that dataset.
From the tool's definition The tool is explicitly named 'delete_dataset' with description 'Delete a dataset and all its items.' This is an irreversible deletion operation affecting both the dataset container and all contained items.
Attacks that exploit this kind of access
Delete a dataset and all its items. It is categorised as a Destructive tool in the Langfuse Mcp Python MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Langfuse Mcp Python MCP server in PolicyLayer and add a rule for delete_dataset: 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 Python. Nothing to install.
delete_dataset 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 delete_dataset 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 delete_dataset. 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.
delete_dataset is provided by the Langfuse Mcp Python MCP server (log-logn/langfuse-mcp-python). 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 →