run · Vending Machine MCP: Risk & Policy

WHAT IT DOES

What run does on Vending Machine

AI agents invoke run to trigger actions in Vending Machine. 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 needs a policy

This tool runs arbitrary marketplace scripts identified by code. The execution of scripts whose behavior depends on the supplied vending code places this in the Execute category. Severity is high because script execution can have broad side effects depending on what the script does (could modify systems, access data, trigger external operations).

From the tool's definition Tool name is 'run' and description states 'Run a marketplace script by its vending code'. The verb 'Run' combined with 'script' execution indicates this tool executes external code or operations whose effects depend on the script argument provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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

FAQ

Questions about run

What does the run tool do? +

Run a marketplace script by its vending code (e.g. S-7K2M). It is categorised as a Execute tool in the Vending Machine 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 Vending Machine 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 Vending Machine. 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 Vending Machine MCP server (yokiidesu/vending-machine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.