// SCAN REPORT

Mcp Upload

6 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 2 Jul 2026

2 can modify or destroy data

4 read-only

6 tools total

Community server · catalogue entry verified 02/07/2026

How to control Mcp Upload ↓

TOOL MAP

What Mcp Upload exposes to your agents

Read (4) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Mcp Upload tools

Write · Medium upload_file This tool creates new data in a persistent storage system (objekt.sh), making it a Write operation. Write · High upload_from_sandbox This tool creates new data (file upload to storage service) with persistent, reversible effects.

2 of Mcp Upload's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Mcp Upload

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Upload, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "upload_file": {
    "limits": [
      {
        "counter": "upload_file_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_connection": {
    "limits": [
      {
        "counter": "check_connection_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Mcp Upload — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP UPLOAD →

Instant setup, no code required.

FULL CATALOGUE

All 6 Mcp Upload tools

WRITE 2 tools

Write upload_file Upload a file to objekt.sh storage. Accepts a host file path OR base64/raw content. For files on the HOST fil Write upload_from_sandbox Upload a file from a sandbox/container path (e.g. /mnt/user-data/, /home/claude/) that the host cannot access.

READ 4 tools

Read check_connection Test connectivity to api.objekt.sh. Use this to diagnose sandbox egress issues. If it fails, the user needs to Read get_file Get a file from objekt.sh by name. Returns a link to the file without downloading the content. Read get_pricing Get current storage pricing and limits from objekt.sh. Read get_version Returns the installed version of the Objekt.sh MCP server.

FAQ

Questions about Mcp Upload

How do I prevent bulk modifications through Mcp Upload? +

The Mcp Upload server has 2 write tools including upload_file, upload_from_sandbox. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Mcp Upload.

How many tools does the Mcp Upload MCP server expose? +

6 tools across 2 categories: Read, Write. 4 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Mcp Upload? +

Register the Mcp Upload MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Mcp Upload tool call.

Deterministic rules across all 6 Mcp Upload tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP UPLOAD →

Instant setup, no code required.

6 Mcp Upload tools catalogued and risk-classified — across an index of 43,000+ MCP servers.