This record as markdown: /tools/aapanel-mcp/site-backup.md
What site_backup does on Aapanel
AI agents use site_backup to create or update resources in Aapanel, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aapanel environment.
Why site_backup is rated Medium
Backup creation falls under Write category—it creates new data (backup files) reversibly without destroying or permanently altering existing data. Severity is medium because misuse could create excessive storage consumption or resource exhaustion, but the operation itself is not destructive.
From the tool's definition Tool name 'site_backup' and description 'Create a backup of a website' indicate data creation/export operation. Backup creation is a reversible write operation that generates new backup artifacts without modifying or deleting the original site data.
Attacks that exploit this kind of access
The rule that runs site_backup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For site_backup, this is the rule to start with:
site_backup 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 Aapanel, apply this rule, and every site_backup call is checked against it from then on.
Questions about site_backup
Create a backup of a website. It is categorised as a Write tool in the Aapanel MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aapanel MCP server in PolicyLayer and add a rule for site_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 Aapanel. Nothing to install.
site_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 site_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 site_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.
site_backup is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
This server
Across the catalogue