Call contracts on connected chains
Executes smart contract functions
Part of the Universal Blockchain MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke call_contract to trigger processes or run actions in Universal Blockchain. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
call_contract can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
call_contract:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: true See the full Universal Blockchain policy for all 17 tools.
Agents calling execute-class tools like call_contract have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
call_contract is one of the high-risk operations in Universal Blockchain. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Call contracts on connected chains. It is categorised as a Execute tool in the Universal Blockchain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for call_contract. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Universal Blockchain MCP server.
call_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 call_contract rule in your Intercept 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 Intercept policy for call_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.
call_contract is provided by the Universal Blockchain MCP server (universal-blockchain-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept