gcp_logging_delete_log

Delete all entries for a log name

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

What gcp_logging_delete_log does on GCP MCP Server

AI agents call gcp_logging_delete_log 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_log is rated Critical

This tool permanently deletes log entries without the possibility of recovery. Deleting logs is a destructive action that cannot be undone and eliminates audit trails and operational history. The blast radius is high because removing logs could obscure security incidents, compliance violations, or system failures, and disable forensic investigation.

From the tool's definition Tool name contains 'delete_log' and description states 'Delete all entries for a log name' — this irreversibly removes log data in bulk.

Risk signalsBulk/mass operation — affects multiple targets

Questions about gcp_logging_delete_log

What does the gcp_logging_delete_log tool do? +

Delete all entries for a log name. 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_log? +

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

gcp_logging_delete_log 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_log? +

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

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

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