Returns the average time between blocks in seconds
AI agents call get_block_interval to retrieve information from MCP Blockchain Query Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves aggregated blockchain statistics from a read-only API. It does not create, modify, delete, or execute any operations—it only queries and returns existing blockchain data. The potential for misuse is minimal, as returning public blockchain metrics cannot harm systems or data integrity.
From the tool's definition Tool name 'get_block_interval' and description 'Returns the average time between blocks in seconds' indicate a pure data retrieval operation with no side effects.
Attacks that exploit this kind of access
Returns the average time between blocks in seconds. It is categorised as a Read tool in the MCP Blockchain Query Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Blockchain Query Server MCP server in PolicyLayer and add a rule for get_block_interval: 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 MCP Blockchain Query Server. Nothing to install.
get_block_interval 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 get_block_interval 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 get_block_interval. 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.
get_block_interval is provided by the MCP Blockchain Query Server MCP server (pavel-bc/mcp-blockchain-query). 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 →