List all log names in the project
AI agents call logging_list_logs to retrieve information from Google Cloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and lists existing log names—a pure data retrieval operation with no side effects, no data modification, no code execution, and no destructive capability. It is informational only and has minimal blast radius if misused by an AI agent (disclosure of log names, which are typically low-sensitivity metadata).
From the tool's definition Tool name 'logging_list_logs' and description 'List all log names in the project' indicate a read-only operation that retrieves log metadata without modification or execution.
Attacks that exploit this kind of access
List all log names in the project. It is categorised as a Read tool in the Google Cloud MCP Server, which means it retrieves data without modifying state.
Register the Google Cloud MCP server in PolicyLayer and add a rule for logging_list_logs: 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_list_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the logging_list_logs 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_list_logs. 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_list_logs 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.
logging_list_logs is one line of Google Cloud's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →