gcp_rm_delete_project

Delete (schedule for deletion) a GCP project

SERVERGCP MCP Server SOURCEahmedselimmansor-ctrl/gcp_mcp_server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-rm-delete-project.md

What gcp_rm_delete_project does on GCP MCP Server

AI agents call gcp_rm_delete_project to permanently remove resources in GCP MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why gcp_rm_delete_project is rated Critical

This tool irreversibly deletes or schedules for deletion an entire GCP project, which destroys all resources, data, and configurations within it. This is a destructive action that cannot be undone and represents the highest severity risk—deletion of organizational infrastructure and potentially all associated data. The action is permanent even if scheduled, making it Destructive rather than Execute.

From the tool's definition Delete (schedule for deletion) a GCP project

Questions about gcp_rm_delete_project

What does the gcp_rm_delete_project tool do? +

Delete (schedule for deletion) a GCP project. It is categorised as a Destructive tool in the GCP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on gcp_rm_delete_project? +

Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_rm_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 GCP MCP Server. Nothing to install.

What risk level is gcp_rm_delete_project? +

gcp_rm_delete_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gcp_rm_delete_project? +

Yes. Add a rate_limit block to the gcp_rm_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.

How do I block gcp_rm_delete_project completely? +

Set action: deny in the PolicyLayer policy for gcp_rm_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.

What MCP server provides gcp_rm_delete_project? +

gcp_rm_delete_project is provided by the GCP MCP Server MCP server (ahmedselimmansor-ctrl/gcp_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GCP MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GCP MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.