foundry_install · HashPilot MCP: Risk & Policy

WHAT IT DOES

What foundry_install does on HashPilot

AI agents invoke foundry_install to trigger actions in HashPilot. 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 foundry_install needs a policy

This tool runs an external git command (git submodule add) to fetch and install third-party code into the project. It executes filesystem and git operations whose effects depend on the provided org/repo argument. Installing arbitrary external dependencies from git repositories poses a high risk: malicious packages could introduce supply-chain attacks, backdoors, or malicious code into the codebase.

From the tool's definition 'Install a dependency via git submodule' — executes a git submodule add operation on the filesystem, triggering external git operations and modifying the repository structure

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

foundry_install Rate-limited

foundry_install 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": {
    "foundry_install": {
      "limits": [
        {
          "counter": "foundry_install_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 HashPilot, so you can run agents against it safely.

FAQ

Questions about foundry_install

What does the foundry_install tool do? +

Install a dependency via git submodule. Examples: forge-std, openzeppelin-contracts. Use format: org/repo (e.g.,. It is categorised as a Execute tool in the HashPilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on foundry_install? +

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

What risk level is foundry_install? +

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

Can I rate-limit foundry_install? +

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

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

foundry_install is provided by the HashPilot MCP server (justmert/hashpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.