AI agents call delete_script_project_tool to permanently remove resources in Apps Script MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of an entire Apps Script project cannot be undone and represents a permanent loss of code, configurations, and potentially associated resources. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While high severity rather than critical because the blast radius is scoped to a single project (not system-wide), the irreversible nature…
From the tool's definition Tool name 'delete_script_project_tool' with description 'Delete an Apps Script project.' directly indicates irreversible deletion of a project and all its associated code, deployments, and data.
Documented attack patterns abuse exactly the kind of access delete_script_project_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apps Script MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_script_project_tool:
{
"version": "1",
"default": "deny",
"hide": [
"delete_script_project_tool"
]
} delete_script_project_tool 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.
Delete an Apps Script project. It is categorised as a Destructive tool in the Apps Script MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Apps Script MCP server in PolicyLayer and add a rule for delete_script_project_tool: 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 Apps Script MCP. Nothing to install.
delete_script_project_tool 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_script_project_tool 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_script_project_tool. 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_script_project_tool is provided by the Apps Script MCP server (sam-ent/google-automation-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apps Script MCP, 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.
60 Apps Script MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.