AI agents call get_backup_plan to retrieve information from Storage without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about an existing backup plan without creating, modifying, or deleting any resources. It is a simple query/fetch operation with no side effects, fitting the Read category. Severity is low since it only exposes backup plan metadata that is typically not sensitive enough to warrant higher classification, though access control may limit exposure.
From the tool's definition Tool name 'get_backup_plan' and description 'Gets a backup plan' indicate data retrieval without modification. The verb 'gets' is a read operation that retrieves backup plan configuration/metadata.
Attacks that exploit this kind of access
Gets a backup plan. It is categorised as a Read tool in the Storage MCP Server, which means it retrieves data without modifying state.
Register the Storage MCP server in PolicyLayer and add a rule for get_backup_plan: 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 Storage. Nothing to install.
get_backup_plan 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_plan 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_plan. 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_plan is provided by the Storage MCP server (@google-cloud/storage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.