Medium Risk

call_contract_function

Call any function on a smart contract on the COTI blockchain. Supports both read-only (view/pure) functions and state-changing (write) functions. Read-only functions return data without creating a transaction. State-changing functions create transactions and may require gas_limit. Returns the fun...

Handles credentials or secrets (private_key)

Part of the COTI MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use call_contract_function to create or modify resources in COTI MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call call_contract_function repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach COTI MCP Server.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

davibauer-coti-mcp.yaml
tools:
  call_contract_function:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full COTI MCP Server policy for all 44 tools.

Tool Name call_contract_function
Category Write
Risk Level Medium

View all 44 tools →

Agents calling write-class tools like call_contract_function have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the call_contract_function tool do? +

Call any function on a smart contract on the COTI blockchain. Supports both read-only (view/pure) functions and state-changing (write) functions. Read-only functions return data without creating a transaction. State-changing functions create transactions and may require gas_limit. Returns the function result in a human-readable format.. It is categorised as a Write tool in the COTI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on call_contract_function? +

Add a rule in your Intercept YAML policy under the tools section for call_contract_function. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the COTI MCP Server MCP server.

What risk level is call_contract_function? +

call_contract_function is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit call_contract_function? +

Yes. Add a rate_limit block to the call_contract_function 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.

How do I block call_contract_function completely? +

Set action: deny in the Intercept policy for call_contract_function. 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.

What MCP server provides call_contract_function? +

call_contract_function is provided by the COTI MCP Server MCP server (davibauer/coti-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.