This record as markdown: /tools/com-googleapis-stitch-mcp/delete-project.md
What delete_project does on Mcp
AI agents call delete_project to permanently remove resources in Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Required. Identifier. The resource name of the project to delete. Format: `projects/{project}` Example: `projects/4044680601076201931` |
Parameters from the server's own tool schema.
Why delete_project is rated Critical
The tool irreversibly deletes data (an entire project) with no recovery mechanism. This is a classic destructive operation that cannot be reversed. While the impact is scoped to a single project rather than system-wide, the permanent loss of potentially significant design work warrants high severity. Confidence is high due to explicit 'cannot be undone' language in the instructions.
From the tool's definition Tool name is 'delete_project' and description states 'Deletes a specific Stitch project' with explicit warning 'This action cannot be undone.'
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, 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, apply this rule, and every delete_project call is checked against it from then on.
Questions about delete_project
Deletes a specific Stitch project using its project name. Instructions for Tool Call: * This action cannot be undone. Please confirm with "yes" or "no" to proceed. It is categorised as a Destructive tool in the Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_project accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the 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. 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 server (https://stitch.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue