gcp_logging_delete_sink

Delete a logging sink

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

Questions about gcp_logging_delete_sink

What does the gcp_logging_delete_sink tool do? +

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.

How do I enforce a policy on gcp_logging_delete_sink? +

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.

What risk level is gcp_logging_delete_sink? +

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.

Can I rate-limit gcp_logging_delete_sink? +

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.

How do I block gcp_logging_delete_sink completely? +

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.

What MCP server provides gcp_logging_delete_sink? +

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.

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