remote_write · Mcp Remote Agent MCP: Risk & Policy

WHAT IT DOES

What remote_write does on Mcp Remote Agent

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

WHY IT NEEDS A POLICY

Why remote_write needs a policy

This tool creates or modifies files on remote Linux servers, which is a reversible write operation. While the action itself is reversible (files can be re-written or restored), the high severity reflects the significant blast radius of an AI agent writing arbitrary files to production Linux systems—potentially overwriting critical configurations, application code, or data.

From the tool's definition Tool name 'remote_write' and description 'Write file to remote workspace' explicitly indicate file modification capability. The mention of 'expectedEtag' for concurrency control confirms write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remote_write Rate-limited

remote_write 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": {
    "remote_write": {
      "limits": [
        {
          "counter": "remote_write_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 Mcp Remote Agent, so you can run agents against it safely.

FAQ

Questions about remote_write

What does the remote_write tool do? +

Write file to remote workspace. Auto CRLF→LF and BOM cleanup. Supports optimistic concurrency lock (expectedEtag). It is categorised as a Write tool in the Mcp Remote Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on remote_write? +

Register the Mcp Remote Agent MCP server in PolicyLayer and add a rule for remote_write: 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 Mcp Remote Agent. Nothing to install.

What risk level is remote_write? +

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

Can I rate-limit remote_write? +

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

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

remote_write is provided by the Mcp Remote Agent MCP server (knownothing20/agentport). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.