upload_directory · Remote Terminal MCP: Risk & Policy

WHAT IT DOES

What upload_directory does on Remote Terminal

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

WHY IT NEEDS A POLICY

Why upload_directory needs a policy

An AI agent can call upload_directory faster than any human can review — one bad instruction and it creates or modifies resources in Remote Terminal by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_directory Rate-limited

upload_directory 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": {
    "upload_directory": {
      "limits": [
        {
          "counter": "upload_directory_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 Terminal, so you can run agents against it safely.

FAQ

Questions about upload_directory

What does the upload_directory tool do? +

Smart directory upload with automatic compression and progress tracking. Automatically decides whether to use compression and background mode based on transfer characteristics. It is categorised as a Write tool in the Remote Terminal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upload_directory? +

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

What risk level is upload_directory? +

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

Can I rate-limit upload_directory? +

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

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

upload_directory is provided by the Remote Terminal MCP server (tim00r/remote-terminal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.