Lists all backup vaults in a given project and location.
AI agents call list_backup_vaults 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 query/retrieval operation to enumerate backup vaults. It has no capability to create, modify, delete, or execute operations. The blast radius is minimal—the only risk is information disclosure of vault metadata within the specified project and location, which is a read-only concern appropriate for the 'Read' category at low severity.
From the tool's definition Tool name is 'list_backup_vaults' and description states it 'Lists all backup vaults in a given project and location.' The verb 'Lists' indicates a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Lists all backup vaults in a given project and location. 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_backup_vaults: 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_backup_vaults 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_backup_vaults 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_backup_vaults. 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_backup_vaults 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 →