Deploy smart contract to Hedera via JSON-RPC. HANDLES: Bytecode deployment, constructor encoding, gas estimation, receipt polling RETURNS: Contract address, transaction hash, deployment details COSTS: Gas fees for contract creation AUTO-KEY: privateKey is OPTIONAL - automatically uses MCP operato...
AI agents invoke rpc_deploy_contract 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.
While smart contract deployment is technically a 'write' operation that creates data (the contract on-chain), it is categorized as Execute rather than Write because: (1) it runs code on an external blockchain system whose side effects are non-trivial and depend entirely on the contract logic supplied by the user, (2) it incurs real financial costs ('Gas fees for contract creation'), and (3) once deployed, the…
From the tool's definition Tool deploys smart contracts to Hedera blockchain via JSON-RPC, handling 'bytecode deployment, constructor encoding, gas estimation, receipt polling' and returning 'contract address, transaction hash, deployment details'.
Attacks that exploit this kind of access
Deploy smart contract to Hedera via JSON-RPC. HANDLES: Bytecode deployment, constructor encoding, gas estimation, receipt polling RETURNS: Contract address, transaction hash, deployment details COSTS: Gas fees for contract creation AUTO-KEY: privateKey is OPTIONAL - automatically uses MCP operator account if not provided USE FOR: Deploying Solidity contracts to Hedera EVM. 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 rpc_deploy_contract: 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.
rpc_deploy_contract 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 rpc_deploy_contract 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 rpc_deploy_contract. 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.
rpc_deploy_contract 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 →