create_backup · Remote Memory MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_backup does on Remote Memory MCP Server

AI agents use create_backup to create or update resources in Remote Memory MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remote Memory MCP Server environment.

WHY IT NEEDS A POLICY

Why create_backup needs a policy

Backup creation is a reversible write operation that produces new data without destructive effects. It does not delete data (Destructive), execute arbitrary code (Execute), or move funds (Financial). While it modifies system state by adding a backup, this is fundamentally a data creation action with minimal blast radius—the worst case is wasted storage or an outdated backup.

From the tool's definition Tool name 'create_backup' and description '현재 메모리 상태의 백업을 생성합니다' (Create a backup of the current memory state) indicate creation of a backup artifact, which is a write operation that creates new data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_backup Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_backup": {
      "limits": [
        {
          "counter": "create_backup_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Remote Memory MCP Server, so you can run agents against it safely.

FAQ

Questions about create_backup

What does the create_backup tool do? +

현재 메모리 상태의 백업을 생성합니다. It is categorised as a Write tool in the Remote Memory MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_backup? +

Register the Remote Memory 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 Remote Memory MCP Server. Nothing to install.

What risk level is create_backup? +

create_backup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_backup? +

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.

How do I block create_backup completely? +

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.

What MCP server provides create_backup? +

create_backup is provided by the Remote Memory MCP Server MCP server (yeomyujun/remote-memory-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.