// SCAN REPORT

RunningHub MCP Server

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

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

Last updated: 30 Jun 2026

2 can modify or destroy data

3 read-only

5 tools total

Community server · catalogue entry verified 30/06/2026

How to control RunningHub MCP Server ↓

TOOL MAP

What RunningHub MCP Server exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous RunningHub MCP Server tools

Execute · High submit_task Based on the server description, this server is used to submit and execute AI tasks on the RunningHub platform. Write · High upload_file The tool creates or modifies data by uploading files to persistent storage, which is a reversible write operation.

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

POLICY

How to control RunningHub MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and RunningHub MCP Server, 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

{
  "get_task_detail": {
    "limits": [
      {
        "counter": "get_task_detail_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 RunningHub MCP Server — 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 RUNNINGHUB →

Instant setup, no code required.

FULL CATALOGUE

All 5 RunningHub MCP Server tools

EXECUTE 1 tools

Execute submit_task submit_task

WRITE 1 tools

Write upload_file upload_file

READ 3 tools

Read get_task_detail get_task_detail Read query_task_outputs query_task_outputs Read sync_task_status sync_task_status

FAQ

Questions about RunningHub MCP Server

How do I prevent bulk modifications through RunningHub MCP Server? +

The RunningHub MCP Server server has 1 write tools including upload_file. 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 RunningHub MCP Server.

How many tools does the RunningHub MCP Server MCP server expose? +

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

How do I enforce a policy on RunningHub MCP Server? +

Register the RunningHub MCP Server 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 RunningHub MCP Server tool call.

Deterministic rules across all 5 RunningHub MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON RUNNINGHUB →

Instant setup, no code required.

5 RunningHub MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.