Execute a read-only call to a Hedera smart contract function and return the
AI agents invoke contract_call to trigger actions in Hedera Toolbox. 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 invokes smart contract execution on a live blockchain network. Although the description indicates read-only semantics, contract functions can perform observable state queries and potentially interact with other contracts or protocols.
From the tool's definition Tool name 'contract_call' and description 'Execute a read-only call to a Hedera smart contract function' explicitly state execution of smart contract code.
Attacks that exploit this kind of access
Execute a read-only call to a Hedera smart contract function and return the. It is categorised as a Execute tool in the Hedera Toolbox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hedera Toolbox MCP server in PolicyLayer and add a rule for contract_call: 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 Hedera Toolbox. Nothing to install.
contract_call 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 contract_call 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 contract_call. 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.
contract_call is provided by the Hedera Toolbox MCP server (mountainmystic/hederatoolbox). 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 →