Call a raw Blockscout API endpoint for advanced or chain-specific data. Do not include query strings in endpoint_path; pass all query parameters via query_params to avoid double-encoding. SUPPORTS PAGINATION: If response includes 'pagination' field, use the provided next_call to get additional pa...
Part of the Blockscout MCP Server server.
Free to start. No card required.
AI agents call direct_api_call to retrieve information from Blockscout MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though direct_api_call only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"direct_api_call": {}
}
}See the full Blockscout MCP Server policy for all 18 tools.
These attack patterns abuse exactly the kind of access direct_api_call gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Call a raw Blockscout API endpoint for advanced or chain-specific data. Do not include query strings in endpoint_path; pass all query parameters via query_params to avoid double-encoding. SUPPORTS PAGINATION: If response includes 'pagination' field, use the provided next_call to get additional pages. Returns: ToolResponse[Any]: Must return ToolResponse[Any] (not ToolResponse[BaseModel]) because specialized handlers can return lists or other types that don't inherit from BaseModel. The dispatcher system supports flexible data structures.. It is categorised as a Read tool in the Blockscout MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Blockscout MCP Server MCP server in PolicyLayer and add a rule for direct_api_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 Blockscout MCP Server. Nothing to install.
direct_api_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 direct_api_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 direct_api_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.
direct_api_call is provided by the Blockscout MCP Server MCP server (https://server.smithery.ai/@blockscout/mcp-server/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Blockscout MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.