Lists all backup plan associations for a given backup plan.
AI agents call list_backup_plan_associations 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 enumerates backup plan associations—a read-only operation that queries data without modifying, deleting, or executing any actions. The worst-case misuse would be information disclosure of backup plan metadata, which has limited blast radius in an observability context.
From the tool's definition Tool name 'list_backup_plan_associations' and description 'Lists all backup plan associations' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Lists all backup plan associations for a given backup plan. 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_plan_associations: 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_plan_associations 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_plan_associations 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_plan_associations. 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_plan_associations 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 →