run_script_with_options · Foundry MCP Project MCP

WHAT IT DOES

What run_script_with_options does on Foundry MCP Project

AI agents invoke run_script_with_options to trigger actions in Foundry MCP Project. 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_with_options needs a policy

Despite the empty description, the tool name and server context strongly indicate this executes arbitrary scripts in a Foundry/Ethereum development environment. Script execution is inherently an Execute category risk because the effects depend entirely on what script content is supplied and run. The 'with_options' suffix suggests parameterization that could be exploited to run unintended code.

From the tool's definition Tool name 'run_script_with_options' indicates execution of scripts. Context shows this is part of a Foundry development server for Ethereum/blockchain development.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_script_with_options Rate-limited

run_script_with_options 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_with_options": {
      "limits": [
        {
          "counter": "run_script_with_options_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 Foundry MCP Project, so you can run agents against it safely.

FAQ

Questions about run_script_with_options

What does the run_script_with_options tool do? +

run_script_with_options. It is categorised as a Execute tool in the Foundry MCP Project 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_with_options? +

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

What risk level is run_script_with_options? +

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

Can I rate-limit run_script_with_options? +

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

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

run_script_with_options is provided by the Foundry MCP Project MCP server (lhemerly/foundry-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.