AI agents use create_backup to create or update resources in Robust Long-Term Memory MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Robust Long-Term Memory MCP environment.
Creating a backup is a write operation—it generates new data artifacts (backup files). While not destructive, it modifies the system state by adding new backup resources. Severity is medium because misuse could create excessive backups consuming storage or overwriting legitimate backups, but the operation is reversible.
From the tool's definition Tool name 'create_backup' indicates creation of a backup file or snapshot, a write operation that generates new data. The description is empty, limiting direct evidence from documentation.
Documented attack patterns abuse exactly the kind of access create_backup gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Robust Long-Term Memory MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_backup:
{
"version": "1",
"default": "deny",
"tools": {
"create_backup": {
"limits": [
{
"counter": "create_backup_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Free to start. No card required.
create_backup. It is categorised as a Write tool in the Robust Long-Term Memory MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Robust Long-Term Memory 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 Robust Long-Term Memory MCP. 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 Robust Long-Term Memory MCP server (rotoslider/long-term-memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Robust Long-Term Memory MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Robust Long-Term Memory MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.