gcp_pubsub_delete_topic

Delete a Pub/Sub topic

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-pubsub-delete-topic.md

What gcp_pubsub_delete_topic does on GCP MCP Server

AI agents call gcp_pubsub_delete_topic 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_pubsub_delete_topic is rated Critical

This tool performs an irreversible destructive action (deletion) on a GCP resource. Once a Pub/Sub topic is deleted, it cannot be recovered, and any messages or subscriptions associated with it are lost. The blast radius depends on the topic's criticality and how many applications depend on it, but the operation is fundamentally non-undoable, placing it in the Destructive category with high severity.

From the tool's definition Tool name explicitly includes 'delete' and description states 'Delete a Pub/Sub topic'. Deleting a topic is an irreversible operation that removes the topic and typically its associated messages and subscriptions.

Questions about gcp_pubsub_delete_topic

What does the gcp_pubsub_delete_topic tool do? +

Delete a Pub/Sub topic. 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_pubsub_delete_topic? +

Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_pubsub_delete_topic: 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_pubsub_delete_topic? +

gcp_pubsub_delete_topic 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_pubsub_delete_topic? +

Yes. Add a rate_limit block to the gcp_pubsub_delete_topic 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_pubsub_delete_topic completely? +

Set action: deny in the PolicyLayer policy for gcp_pubsub_delete_topic. 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_pubsub_delete_topic? +

gcp_pubsub_delete_topic 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.