call_read_only_function

Call a read-only function on a smart contract (no signing required).

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/call-read-only-function.md

WHAT IT DOES

What call_read_only_function does on Aibtc

AI agents call call_read_only_function to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why call_read_only_function is rated Low

This tool queries smart contract state and returns data without executing state-changing transactions. The read-only nature means it has no ability to modify data, execute arbitrary code, or cause irreversible effects. Severity is low as misuse would only result in information disclosure, not asset loss or operational damage.

From the tool's definition Tool name explicitly states 'read_only' and description confirms 'no signing required', indicating retrieval without state modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs call_read_only_function safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For call_read_only_function, this is the rule to start with:

call_read_only_function Allowed

call_read_only_function is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "call_read_only_function": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every call_read_only_function call is checked against it from then on.

FAQ

Questions about call_read_only_function

What does the call_read_only_function tool do? +

Call a read-only function on a smart contract (no signing required). It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on call_read_only_function? +

Register the Aibtc MCP server in PolicyLayer and add a rule for call_read_only_function: 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 Aibtc. Nothing to install.

What risk level is call_read_only_function? +

call_read_only_function is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit call_read_only_function? +

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

How do I block call_read_only_function completely? +

Set action: deny in the PolicyLayer policy for call_read_only_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_read_only_function? +

call_read_only_function is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →