run_script · MCPMake MCP: Risk & Policy

WHAT IT DOES

What run_script does on MCPMake

AI agents invoke run_script to trigger actions in MCPMake. 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_script needs a policy

This tool executes arbitrary Python scripts with user-supplied arguments. Even though the scripts are pre-registered, execution remains contingent on runtime arguments, making outcomes unpredictable. An LLM could invoke this with malicious or unintended arguments causing uncontrolled side effects (file I/O, network calls, resource consumption).

From the tool's definition Tool description states 'Run a registered script with arguments'. The server enables 'execution of Python scripts' with 'automatic LLM-extracted argument schemas'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_script Rate-limited

run_script 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_script": {
      "limits": [
        {
          "counter": "run_script_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 MCPMake, so you can run agents against it safely.

FAQ

Questions about run_script

What does the run_script tool do? +

Run a registered script with arguments. It is categorised as a Execute tool in the MCPMake 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_script? +

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

What risk level is run_script? +

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

Can I rate-limit run_script? +

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

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

run_script is provided by the MCPMake MCP server (shex1627/mcpmake). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.