terminal_upload_file · Mcp Shellkeeper MCP: Risk & Policy

WHAT IT DOES

What terminal_upload_file does on Mcp Shellkeeper

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

WHY IT NEEDS A POLICY

Why terminal_upload_file needs a policy

This tool uploads files to a remote server, which creates or modifies data on that server. While not destructive (the operation is reversible via deletion), it goes beyond read-only operations and qualifies as Write. The severity is high because an AI agent misusing this could upload malicious files, overwrite critical configurations, or introduce security vulnerabilities on the remote system.

From the tool's definition tool name is 'terminal_upload_file' and description states 'Upload a file from local machine to remote server through the terminal session' - directly modifies remote system state by adding/uploading files

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

terminal_upload_file Rate-limited

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

FAQ

Questions about terminal_upload_file

What does the terminal_upload_file tool do? +

Upload a file from local machine to remote server through the terminal session. It is categorised as a Write tool in the Mcp Shellkeeper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on terminal_upload_file? +

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

What risk level is terminal_upload_file? +

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

Can I rate-limit terminal_upload_file? +

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

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

terminal_upload_file is provided by the Mcp Shellkeeper MCP server (mcp-shellkeeper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.