Delete an existing dataset.
AI agents call tensorus_delete_dataset to permanently remove resources in Tensorus MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Dataset deletion is an irreversible operation that destroys data without possibility of recovery through normal means. This qualifies as Destructive rather than Write (which implies reversible modification). The high severity reflects the potential loss of significant stored tensor data and any dependent operations. Confidence is high because the intent is unambiguous from both the name and description.
From the tool's definition Tool name 'tensorus_delete_dataset' explicitly performs deletion of an existing dataset. Description states 'Delete an existing dataset,' indicating irreversible removal of data.
Attacks that exploit this kind of access
Delete an existing dataset. It is categorised as a Destructive tool in the Tensorus MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tensorus MCP server in PolicyLayer and add a rule for tensorus_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 Tensorus MCP. Nothing to install.
tensorus_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 tensorus_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 tensorus_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.
tensorus_delete_dataset is provided by the Tensorus MCP server (tensorus/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 →