Create a new backup
AI agents use create_backup to create or update resources in HC3 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HC3 MCP Server environment.
Creating backups is a write operation that generates new data artifacts. While not destructive itself, backups are critical system data and unauthorized backup creation could be part of an attack workflow (exfiltration). Severity is high due to potential access to sensitive smart home configuration data including device credentials, automations, and personal routines that could be contained in the backup.
From the tool's definition Tool name 'create_backup' and description 'Create a new backup' indicates creation of a backup file, which is a write operation that creates new data/files in the system.
Attacks that exploit this kind of access
Create a new backup. It is categorised as a Write tool in the HC3 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HC3 MCP Server MCP server in PolicyLayer and add a rule for create_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 HC3 MCP Server. Nothing to install.
create_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 create_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 create_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.
create_backup is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →