Execute a read-only call to a smart contract
AI agents invoke call to trigger actions in Monad MCP Server. 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 the 'read-only' qualifier limits destructive potential compared to state-modifying calls, executing arbitrary smart contract code still qualifies as Execute category per the taxonomy: 'runs code...whose effects depend on arguments.' An AI agent could invoke complex or malicious contracts with side effects (even if technically read-only), loops, or resource consumption.
From the tool's definition Tool description states 'Execute a read-only call to a smart contract.' The verb 'Execute' indicates this runs code (smart contract logic) rather than passively retrieving data.
Attacks that exploit this kind of access
Execute a read-only call to a smart contract. It is categorised as a Execute tool in the Monad MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Monad MCP Server MCP server in PolicyLayer and add a rule for 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 Monad MCP Server. Nothing to install.
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 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 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.
call is provided by the Monad MCP Server MCP server (tairon-ai/monad-mcp). 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 →