AI agents call delete_dataset to permanently remove resources in TestRail MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations are inherently destructive as they permanently remove data that cannot be recovered without backups. In a test management system like TestRail, deleting a dataset could remove critical test data, configurations, or results needed for test execution and reporting. The absence of a description lowers confidence slightly, but the naming convention is explicit enough to classify with high confidence.
From the tool's definition Tool name is 'delete_dataset' with no descriptive text provided. The 'delete_' prefix indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_dataset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TestRail MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_dataset:
{
"version": "1",
"default": "deny",
"hide": [
"delete_dataset"
]
}delete_dataset disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_dataset. It is categorised as a Destructive tool in the TestRail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TestRail MCP Server 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 TestRail MCP Server. 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 TestRail MCP Server MCP server (sker65/testrail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TestRail MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 TestRail MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.