AI agents use restore_backup to create or update resources in Storage — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Storage environment.
Restoring a backup writes data to a target environment, potentially overwriting existing data on Compute Instances or Disks. While it could be considered destructive if it overwrites existing data, restores are generally intended to be recovery operations that create or overwrite resources in a controlled way.
From the tool's definition 'Restores a Backup resource to a target environment' — restore operation writes/overwrites data in the target environment for Compute Instances and Disks
Attacks that exploit this kind of access
Restores a Backup resource to a target environment. Supports Compute Instances and Disks. It is categorised as a Write tool in the Storage MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Storage MCP server in PolicyLayer and add a rule for restore_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.
restore_backup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the restore_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 restore_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.
restore_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.