Delete a trigger by ID. Use trigger_list to find IDs.
AI agents call trigger_delete to permanently remove resources in Gworkspace — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently deletes an Apps Script trigger by its ID. Trigger deletion is irreversible; once a trigger is removed, any scheduled or event-driven automation it controlled stops firing, potentially breaking workflows. This is a destructive, non-reversible action with high blast radius if misused by an AI agent.
From the tool's definition "Delete a trigger by ID" — explicitly deletes a trigger irreversibly
Attacks that exploit this kind of access
Delete a trigger by ID. Use trigger_list to find IDs. It is categorised as a Destructive tool in the Gworkspace MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gworkspace MCP server in PolicyLayer and add a rule for trigger_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 Gworkspace. Nothing to install.
trigger_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 trigger_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 trigger_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.
trigger_delete is provided by the Gworkspace MCP server (leoonic/gworkspace-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 →