cloud_backup_update
Update an existing cloud backup task
This record as markdown: /tools/nasbridge/cloud-backup-update.md
What cloud_backup_update does on Nasbridge
AI agents use cloud_backup_update to create or update resources in Nasbridge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nasbridge environment.
Why cloud_backup_update is rated Medium
This tool creates or modifies data reversibly by updating backup task configuration. While it has side effects (changing backup behavior), it is not destructive (data/configs can be reverted) and does not execute arbitrary code or move money. The 'high' severity reflects that misconfiguring cloud backups could compromise data protection strategy, affecting backup integrity and disaster recovery capabilities.
From the tool's definition Tool name is 'cloud_backup_update' and description states 'Update an existing cloud backup task' — this modifies configuration of a backup task reversibly without deleting it.
Attacks that exploit this kind of access
The rule that runs cloud_backup_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cloud_backup_update, this is the rule to start with:
cloud_backup_update stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every cloud_backup_update call is checked against it from then on.
Questions about cloud_backup_update
Update an existing cloud backup task. It is categorised as a Write tool in the Nasbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nasbridge MCP server in PolicyLayer and add a rule for cloud_backup_update: 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 Nasbridge. Nothing to install.
cloud_backup_update 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 cloud_backup_update 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 cloud_backup_update. 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.
cloud_backup_update is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue