Delete one or more attachments from a test case.
AI agents call testmo_delete_case_attachments to permanently remove resources in Testmo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (attachments) from test cases without the ability to undo the operation through normal means. While the blast radius is somewhat limited compared to deleting entire test cases, the irreversible nature of deletion and potential loss of important test documentation or evidence places this in the Destructive category with high severity.
From the tool's definition Tool name contains 'delete' and description states 'Delete one or more attachments from a test case.' The action irreversibly removes attachments.
Attacks that exploit this kind of access
Delete one or more attachments from a test case. It is categorised as a Destructive tool in the Testmo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Testmo MCP server in PolicyLayer and add a rule for testmo_delete_case_attachments: 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 Testmo. Nothing to install.
testmo_delete_case_attachments 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 testmo_delete_case_attachments 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 testmo_delete_case_attachments. 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.
testmo_delete_case_attachments is provided by the Testmo MCP server (strelec00/testmo-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 →