Get information about recent blocks on the network
AI agents call telos_recent_blocks to retrieve information from Telos Network MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries blockchain state (recent block data) without modifying, executing code, deleting data, or moving funds. It is a passive read operation similar to fetching historical or current network information. The low severity reflects minimal blast radius—misuse would only expose public blockchain data already visible on the network.
From the tool's definition Tool name 'telos_recent_blocks' and description 'Get information about recent blocks on the network' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get information about recent blocks on the network. It is categorised as a Read tool in the Telos Network MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Telos Network MCP Server MCP server in PolicyLayer and add a rule for telos_recent_blocks: 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 Telos Network MCP Server. Nothing to install.
telos_recent_blocks 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 telos_recent_blocks 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 telos_recent_blocks. 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.
telos_recent_blocks is provided by the Telos Network MCP Server MCP server (tairon-ai/telos-mcp). 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 →