Permanently delete an experiment and its spans. This action cannot be undone.
AI agents call delete_experiment to permanently remove resources in Respan MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool meets the Destructive category definition as it irreversibly deletes data (an experiment and its spans) and cannot be undone. While the blast radius depends on experiment scope, the permanent nature and inability to recover qualifies this as high severity. The confidence is very high due to explicit destructive language in the description.
From the tool's definition Tool description explicitly states 'Permanently delete an experiment' and 'This action cannot be undone.' The use of 'Permanently' and the undo-negation clearly indicate irreversible deletion of data.
Attacks that exploit this kind of access
Permanently delete an experiment and its spans. This action cannot be undone. It is categorised as a Destructive tool in the Respan MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Respan MCP Server MCP server in PolicyLayer and add a rule for delete_experiment: 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 Respan MCP Server. Nothing to install.
delete_experiment 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_experiment 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_experiment. 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_experiment is provided by the Respan MCP Server MCP server (respanai/respan-mcp). 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 →