Delete a resource (with dependency checking)
AI agents call delete_resource to permanently remove resources in Terragrunt GCP Tool MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of infrastructure resources is irreversible and cannot be undone. Even with dependency checking, this tool permanently removes cloud infrastructure, data, or services. The blast radius is critical—misuse could destroy production environments, databases, or essential services. This is the most severe category applicable.
From the tool's definition Tool name explicitly states 'delete_resource' and description confirms deletion operation. Operates on GCP infrastructure managed through Terragrunt, affecting real cloud resources.
Attacks that exploit this kind of access
Delete a resource (with dependency checking). It is categorised as a Destructive tool in the Terragrunt GCP Tool MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Terragrunt GCP Tool MCP server in PolicyLayer and add a rule for delete_resource: 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 Terragrunt GCP Tool MCP. Nothing to install.
delete_resource 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_resource 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_resource. 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_resource is provided by the Terragrunt GCP Tool MCP server (spolspol/terragrunt-gcp-tool-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 →