List all log sinks in the project
AI agents call logging_list_log_sinks 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 retrieves and displays existing log sink configurations from Google Cloud Logging. It performs a query-only operation that does not create, modify, delete, or execute any resources. The blast radius of misuse is minimal—an attacker would only gain visibility into logging configurations, not the ability to alter them or access log data itself.
From the tool's definition Tool name and description indicate listing/querying: 'List all log sinks in the project'. The verb 'list' and action 'log sinks' (configuration metadata) confirm this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all log sinks 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_log_sinks: 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_log_sinks 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_log_sinks 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_log_sinks. 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_log_sinks 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 →