This record as markdown: /tools/mcp-test-servers/delete-project.md
What delete-project does on Mcp Test Servers
AI agents call delete-project to permanently remove resources in Mcp Test Servers, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete-project is rated Critical
Deletion operations are classified as Destructive per the schema rules, as they cannot be undone. The high severity reflects that an AI agent misusing this tool could permanently remove entire projects, causing significant data loss. Confidence is 0.95 rather than 1.0 because we lack detail on what 'project' encompasses and whether there are safeguards like soft-deletes, but the explicit 'delete' verb is unambiguous.
From the tool's definition Tool name is 'delete-project' with description 'Delete a project'. The verb 'Delete' combined with 'project' (a likely substantive resource) indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete-project safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Test Servers, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-project, this is the rule to start with:
delete-project is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Test Servers, apply this rule, and every delete-project call is checked against it from then on.
Questions about delete-project
Delete a project. It is categorised as a Destructive tool in the Mcp Test Servers MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Test Servers MCP server in PolicyLayer and add a rule for delete-project: 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 Test Servers. Nothing to install.
delete-project 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-project 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-project. 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-project is provided by the Mcp Test Servers MCP server (msfeldstein/mcp-test-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Test Servers, and thousands of servers like it.
Across the catalogue