Delete a test plan or test file
AI agents call test_artifact_delete to permanently remove resources in MCP Playwright Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes test plans or test files, which is an irreversible destructive operation. Misuse by an AI agent could result in permanent loss of test plans and test files, which may be critical assets in a testing workflow. The description clearly states deletion with no mention of recovery or soft-delete mechanisms.
From the tool's definition Tool name 'test_artifact_delete' and description 'Delete a test plan or test file' explicitly indicate irreversible deletion of test artifacts.
Attacks that exploit this kind of access
Delete a test plan or test file. It is categorised as a Destructive tool in the MCP Playwright Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Playwright Server MCP server in PolicyLayer and add a rule for test_artifact_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 MCP Playwright Server. Nothing to install.
test_artifact_delete 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 test_artifact_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.
Set action: deny in the PolicyLayer policy for test_artifact_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.
test_artifact_delete is provided by the MCP Playwright Server MCP server (j0hanz/playwright-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 →