Delete a log
AI agents call logging_delete_log to permanently remove resources in Google Cloud — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes log data from Google Cloud Logging, which cannot be undone. Deletion of logs is a destructive action with potential compliance and forensic investigation implications. The high severity reflects the irreversible nature and potential business impact of losing audit trails and operational logs.
From the tool's definition Tool name 'logging_delete_log' and description 'Delete a log' explicitly indicate irreversible deletion of logging data.
Attacks that exploit this kind of access
Delete a log. It is categorised as a Destructive tool in the Google Cloud MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Cloud MCP server in PolicyLayer and add a rule for 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 Google Cloud. Nothing to install.
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.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
logging_delete_log is provided by the Google Cloud MCP server (lockon-n/google-cloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →