AI agents call get_backup 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 or queries backup information without causing side effects. It performs a read-only operation consistent with data retrieval. The use of 'Gets' (past tense of get, meaning to retrieve) confirms this is a Read operation. No data is created, modified, deleted, or executed. Severity is low because reading backup metadata poses minimal risk compared to tools that modify or delete backups.
From the tool's definition Tool name 'get_backup' and description 'Gets a backup' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Gets a backup. 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: 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 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 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. 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 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.