Clear all test cases to start fresh with new requirements.
AI agents call clear_test_cases to permanently remove resources in MCPGex — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes all stored test cases. While the data is application-level (regex test cases rather than critical business data), the action is irreversible and cannot be undone without re-adding each test case manually. It qualifies as Destructive due to the bulk, permanent nature of the deletion.
From the tool's definition 'Clear all test cases to start fresh' — irreversibly removes all existing test cases
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access clear_test_cases gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCPGex, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_test_cases:
{
"version": "1",
"default": "deny",
"hide": [
"clear_test_cases"
]
}clear_test_cases 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.
Clear all test cases to start fresh with new requirements. It is categorised as a Destructive tool in the MCPGex MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCPGex MCP server in PolicyLayer and add a rule for clear_test_cases: 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 MCPGex. Nothing to install.
clear_test_cases 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 clear_test_cases 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 clear_test_cases. 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.
clear_test_cases is provided by the MCPGex MCP server (patzedi/mcpgex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCPGex, 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.
4 MCPGex tools catalogued and risk-classified — across an index of 43,000+ MCP servers.