Manage Foundry project lifecycle operations. OPERATIONS: - init: Initialize new Foundry project with templates - install: Install git submodule dependency (e.g., forge-std) - update: Update all dependencies - remove: Remove a dependency - clean: Clean build artifacts - build: Compile contracts wi...
AI agents invoke foundry_project 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 various Foundry CLI operations including compiling Solidity smart contracts, managing git submodule dependencies, and running build processes. These are external operations that trigger execution of code and system-level commands (forge build, forge install, etc.).
From the tool's definition Manage Foundry project lifecycle operations... init, install, update, remove, clean, build, compile contracts, fmt, inspect, get_artifacts, snapshot
Attacks that exploit this kind of access
Manage Foundry project lifecycle operations. OPERATIONS: - init: Initialize new Foundry project with templates - install: Install git submodule dependency (e.g., forge-std) - update: Update all dependencies - remove: Remove a dependency - clean: Clean build artifacts - build: Compile contracts with optimization options - fmt: Format Solidity code - inspect: Inspect contract artifacts (ABI, bytecode, storage-layout) - get_artifacts: Retrieve compiled artifacts - snapshot: Create gas usage snapshot for optimization USE FOR: Project setup, dependencies, compilation, and gas optimization. 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_project: 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_project 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_project 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_project. 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_project 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 →