run_python_script_async · MCPHub MCP: Risk & Policy

WHAT IT DOES

What run_python_script_async does on MCPHub

AI agents invoke run_python_script_async to trigger actions in MCPHub. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_python_script_async needs a policy

This tool executes arbitrary Python scripts, making it an Execute category tool. The async execution pattern combined with the absence of any documented safeguards or scope limitations presents a critical severity—an AI agent could run malicious code, exfiltrate data, modify system state, or trigger destructive operations.

From the tool's definition Tool name 'run_python_script_async' explicitly indicates execution of arbitrary Python code asynchronously. The empty description fails to clarify constraints or sandboxing, which escalates risk.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_python_script_async Rate-limited

run_python_script_async stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_python_script_async": {
      "limits": [
        {
          "counter": "run_python_script_async_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCPHub, so you can run agents against it safely.

FAQ

Questions about run_python_script_async

What does the run_python_script_async tool do? +

run_python_script_async. It is categorised as a Execute tool in the MCPHub MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_python_script_async? +

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

What risk level is run_python_script_async? +

run_python_script_async is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_python_script_async? +

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

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

run_python_script_async is provided by the MCPHub MCP server (jayden-dong/mcphub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.