gcp_logging_delete_sink
Delete a logging sink
This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-logging-delete-sink.md
What gcp_logging_delete_sink does on GCP MCP Server
AI agents call gcp_logging_delete_sink 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_logging_delete_sink is rated Critical
This tool irreversibly removes a logging sink configuration from Google Cloud Platform. Deletion of logging infrastructure is a destructive action—once deleted, the sink configuration and its associated routing rules are lost and must be manually recreated. An AI agent misusing this could disrupt log aggregation, monitoring, and compliance by removing critical logging pipelines.
From the tool's definition Tool name contains 'delete' and description states 'Delete a logging sink'. Deletes are irreversible operations that cannot be undone.
Attacks that exploit this kind of access
The rule that runs gcp_logging_delete_sink 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_logging_delete_sink, this is the rule to start with:
gcp_logging_delete_sink 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_logging_delete_sink call is checked against it from then on.
Questions about gcp_logging_delete_sink
Delete a logging sink. 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_logging_delete_sink: 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_logging_delete_sink 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_logging_delete_sink 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_logging_delete_sink. 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_logging_delete_sink 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