Get current Algorand network status including last round, supply, and chain info
AI agents call getNetworkStatus to retrieve information from Algorand MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves immutable blockchain network metadata. It has no side effects, cannot modify state, and poses minimal risk even if called maliciously. Classification as Read is appropriate with low severity.
From the tool's definition Tool name and description indicate it retrieves network status information ("last round, supply, and chain info") with no modification or execution capability. The 'get' prefix and query-only nature confirm this is a read operation.
Attacks that exploit this kind of access
Get current Algorand network status including last round, supply, and chain info. It is categorised as a Read tool in the Algorand MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Algorand MCP Server MCP server in PolicyLayer and add a rule for getNetworkStatus: 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 Algorand MCP Server. Nothing to install.
getNetworkStatus 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 getNetworkStatus 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 getNetworkStatus. 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.
getNetworkStatus is provided by the Algorand MCP Server MCP server (tairon-ai/algorand-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 →