gcp_pubsub_delete_topic
Delete a Pub/Sub topic
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.
Attacks that exploit this kind of access
The rule that runs gcp_pubsub_delete_topic safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GCP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gcp_pubsub_delete_topic, this is the rule to start with:
gcp_pubsub_delete_topic is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect GCP MCP Server, apply this rule, and every gcp_pubsub_delete_topic call is checked against it from then on.
Questions about gcp_pubsub_delete_topic
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.
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.
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.
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.
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.
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.
Across the catalogue