AI agents call deployment_history 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.
deployment_history is a read-only tool that queries and retrieves blockchain deployment information. It filters existing data and exports it in various formats (JSON, CSV, Markdown) but does not create, modify, delete, or execute any transactions or operations.
From the tool's definition The tool description states 'View deployment history with filtering and export.' It enables retrieval and export of historical deployment data without modifying or executing operations.
Attacks that exploit this kind of access
View deployment history with filtering and export. FILTERS: By network, contract name, status EXPORTS: JSON, CSV, or Markdown format USE FOR: Tracking deployments, auditing, documentation. 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 deployment_history: 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.
deployment_history 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 deployment_history 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 deployment_history. 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.
deployment_history 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 →