AI agents call foundry_get_artifacts to retrieve information from HashPilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only operation to retrieve pre-compiled contract artifacts. There are no side effects, no code execution, no data modification, and no destructive actions. While the server interacts with blockchain, this specific tool only retrieves artifact metadata and compiled code stored locally, posing minimal security risk.
From the tool's definition Tool description states 'Get compiled contract artifacts' — a retrieval operation with no modification, deletion, or execution. It reads static files (ABI, bytecode, metadata) from the out/ directory.
Attacks that exploit this kind of access
Get compiled contract artifacts including ABI, bytecode, and metadata from out/ directory. It is categorised as a Read tool in the HashPilot MCP Server, which means it retrieves data without modifying state.
Register the HashPilot MCP server in PolicyLayer and add a rule for foundry_get_artifacts: 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_get_artifacts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the foundry_get_artifacts 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_get_artifacts. 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_get_artifacts 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 →