foundry_update · HashPilot MCP: Risk & Policy

WHAT IT DOES

What foundry_update does on HashPilot

AI agents invoke foundry_update 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_update needs a policy

This tool executes a git command (submodule update) that modifies repository state by pulling in new dependency versions. While it can be partially reversed by pinning to previous commits, it triggers external operations and modifies the working environment. It fits Execute best as it runs an external git operation with side effects dependent on the current state of remote repositories.

From the tool's definition 'Update all git submodule dependencies to their latest versions' — runs a git submodule update operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

foundry_update Rate-limited

foundry_update 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_update": {
      "limits": [
        {
          "counter": "foundry_update_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_update

What does the foundry_update tool do? +

Update all git submodule dependencies to their latest versions. 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_update? +

Register the HashPilot MCP server in PolicyLayer and add a rule for foundry_update: 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_update? +

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

Can I rate-limit foundry_update? +

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

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

foundry_update 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.