Gets a backup vault.
AI agents call get_backup_vault 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 or queries information about a backup vault in GCP's Observability APIs. The verb 'get' is a read operation that returns data without side effects, altering state, or triggering irreversible actions. The low severity reflects that retrieving backup vault metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_backup_vault' and description 'Gets a backup vault' indicate a retrieval operation with no modification or execution of external processes.
Attacks that exploit this kind of access
Gets a backup vault. 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 get_backup_vault: 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.
get_backup_vault 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 get_backup_vault 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 get_backup_vault. 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.
get_backup_vault 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 →