sync_push · Remote Memory MCP Server MCP: Risk & Policy

WHAT IT DOES

What sync_push does on Remote Memory MCP Server

AI agents use sync_push 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 sync_push needs a policy

sync_push pushes local data to a remote GitHub repository, which creates or updates data on the remote system. While the operation is reversible (via git history or further pushes), it modifies the authoritative remote state and could overwrite existing data depending on merge behavior. This is Write-category behavior.

From the tool's definition Tool description in Korean translates to 'Push local data to GitHub', and it is part of a suite that includes destructive operations (delete_entities, delete_observations, delete_relations) and force_sync.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync_push Rate-limited

sync_push 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": {
    "sync_push": {
      "limits": [
        {
          "counter": "sync_push_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 sync_push

What does the sync_push tool do? +

로컬 데이터를 GitHub로 푸시합니다. 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 sync_push? +

Register the Remote Memory MCP Server MCP server in PolicyLayer and add a rule for sync_push: 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 sync_push? +

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

Can I rate-limit sync_push? +

Yes. Add a rate_limit block to the sync_push 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 sync_push completely? +

Set action: deny in the PolicyLayer policy for sync_push. 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 sync_push? +

sync_push 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.