Use this as the primary tool to list the log sinks in a Google Cloud project. Log sinks control how Cloud Logging routes your logs to supported destinations, such as Cloud Storage buckets, BigQuery datasets, or Pub/Sub topics. This is useful for understanding your logging export configurations.
AI agents call list_sinks to retrieve information from Observability without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing log sink configurations in a GCP project. It performs a read-only operation that returns information about how logs are routed, with no capability to create, modify, delete, or execute anything. The blast radius of misuse is minimal—an AI agent could only view logging configurations it may not have access to, which is an information disclosure risk but low severity.
From the tool's definition Tool name is 'list_sinks' and description states it is used to 'list the log sinks' and understand 'logging export configurations'. The verb 'list' indicates retrieval/querying of existing data with no modification or side effects.
Attacks that exploit this kind of access
Use this as the primary tool to list the log sinks in a Google Cloud project. Log sinks control how Cloud Logging routes your logs to supported destinations, such as Cloud Storage buckets, BigQuery datasets, or Pub/Sub topics. This is useful for understanding your logging export configurations. It is categorised as a Read tool in the Observability MCP Server, which means it retrieves data without modifying state.
Register the Observability MCP server in PolicyLayer and add a rule for list_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 Observability. Nothing to install.
list_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 list_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 list_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.
list_sinks is provided by the Observability MCP server (@google-cloud/observability-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 →