requirements_delete

THE RISK

Critical Risk

Why requirements_delete needs a policy

The tool performs an irreversible deletion of requirement data. According to classification rules, destructive operations that cannot be undone take precedence over other categories. In a test management platform, deleting requirements could break test traceability, compliance records, or project documentation, making this a high-severity issue if invoked incorrectly by an AI agent.

From the tool's definition Tool name 'requirements_delete' and description explicitly states 'Delete requirement' with API endpoint showing removal operation. Deletes data irreversibly.

Documented attack patterns abuse exactly the kind of access requirements_delete gives an agent:

POLICY

How to control requirements_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and Testomatio MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for requirements_delete:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "requirements_delete"
  ]
}

requirements_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Testomatio MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Testomatio MCP Server tools

Write requirements_create Create requirement (/api/v2/{project_id}/requirements) Write requirements_update Update requirement (/api/v2/{project_id}/requirements/{id}) Read analytics_stats Enterprise analytics: fetch an aggregated analytics report (/api/v2/{project_id}/analytics Read analytics_tests Enterprise analytics: list tests matching an analytics report (/api/v2/{project_id}/analyt Read milestones_get Get milestone by ID Read milestones_list List milestones (/api/v2/{project_id}/milestones) Read requirements_get Get requirement by ID Read requirements_list List requirements (/api/v2/{project_id}/requirements)

All 10 Testomatio MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Testomatio MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about requirements_delete

What does the requirements_delete tool do? +

Delete requirement (/api/v2/{project_id}/requirements/{id}). It is categorised as a Destructive tool in the Testomatio 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 requirements_delete? +

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

What risk level is requirements_delete? +

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

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

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

requirements_delete is provided by the Testomatio MCP Server MCP server (testomatio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Testomatio MCP Server tool call.

Start from Testomatio MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →