AI agents invoke foundry_anvil_stop 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.
This tool executes a command to terminate a service. While not destructive to persistent data and not read-only, it is an Execute-category action because it triggers an external operation with side effects (halting blockchain infrastructure). The severity is medium: stopping a local node disrupts operations but is reversible (the node can be restarted).
From the tool's definition Tool description states 'Stop the running Anvil local node' — this triggers an external operation (terminating a process) whose effects depend on runtime state.
Attacks that exploit this kind of access
Stop the running Anvil local node. 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.
Register the HashPilot MCP server in PolicyLayer and add a rule for foundry_anvil_stop: 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.
foundry_anvil_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the foundry_anvil_stop 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.
Set action: deny in the PolicyLayer policy for foundry_anvil_stop. 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.
foundry_anvil_stop 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →