Make a static call to a smart contract on any EVM-compatible chain (read-only)
AI agents call static-call to retrieve information from Blockchain MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Static calls (also called view/pure function calls in Solidity) retrieve data from smart contracts without executing state-changing operations. They have no side effects and cannot modify blockchain state. This is the safest category of blockchain interaction. Severity is low because the blast radius is limited to information disclosure of already-public blockchain data.
From the tool's definition Tool description explicitly states "static call to a smart contract" and "read-only". Static calls in EVM terminology are guaranteed non-state-modifying queries.
Attacks that exploit this kind of access
Make a static call to a smart contract on any EVM-compatible chain (read-only). It is categorised as a Read tool in the Blockchain MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Blockchain MCP Server MCP server in PolicyLayer and add a rule for static-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 Blockchain MCP Server. Nothing to install.
static-call 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 static-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 static-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.
static-call is provided by the Blockchain MCP Server MCP server (lienhage/blockchain-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 →