run

Runs a script or file with

SERVERTest SOURCEDave-London/Pare

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-pare-test/run.md

WHAT IT DOES

What run does on Test

AI agents invoke run to trigger actions in Test. 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.

RISK

Why run is rated High

The 'run' tool executes scripts or files, which triggers external code execution whose effects depend entirely on the arguments (which script/file is passed and its contents). This is a classic Execute category tool—it does not merely query data (Read), create reversible changes (Write), or permanently delete data (Destructive), but rather invokes arbitrary code execution.

From the tool's definition Tool name is 'run' and description states it 'Runs a script or file with' (description appears truncated but the intent is clear). The sibling tools on this server include 'ansible-playbook' and 'apply', indicating this is an execution/automation context.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Test, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run, this is the rule to start with:

run Rate-limited

run 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": {
      "limits": [
        {
          "counter": "run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Test, apply this rule, and every run call is checked against it from then on.

FAQ

Questions about run

What does the run tool do? +

Runs a script or file with. It is categorised as a Execute tool in the Test 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? +

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

What risk level is run? +

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

Can I rate-limit run? +

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

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

run is provided by the Test MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Test, and thousands of servers like it.

This server

All 202 Test tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →