Use this as the primary tool to list the log scopes in a Google Cloud project. Log scopes allow you to query logs from multiple projects in a single view. This is useful for centralized logging across a large organization.
AI agents call list_log_scopes 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 performs a read-only query operation to list existing log scopes in a GCP project. It retrieves information for viewing purposes only, with no capability to create, modify, delete, or execute operations. The worst-case misuse would be unauthorized information gathering about the logging configuration, which is a relatively low-severity risk compared to tools that modify or delete data.
From the tool's definition Tool name is 'list_log_scopes' and description states 'list the log scopes' which retrieves/queries data about log scopes without modifying anything. No side effects are mentioned.
Attacks that exploit this kind of access
Use this as the primary tool to list the log scopes in a Google Cloud project. Log scopes allow you to query logs from multiple projects in a single view. This is useful for centralized logging across a large organization. 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_log_scopes: 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_log_scopes 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_log_scopes 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_log_scopes. 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_log_scopes 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 →