Get staking information for an account
AI agents call getStakingInfo 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 queries staking information associated with an account on the Algorand blockchain. It performs a read-only operation that retrieves existing data. There is no code execution, financial transaction, data modification, or destructive action. The blast radius of misuse is minimal — an attacker could only view staking details, not alter them or move funds. This is a standard Read category tool.
From the tool's definition Tool name is 'getStakingInfo' and description states 'Get staking information for an account' — retrieves data without modification or side effects.
Attacks that exploit this kind of access
Get staking information for an account. 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 getStakingInfo: 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.
getStakingInfo 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 getStakingInfo 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 getStakingInfo. 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.
getStakingInfo 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 →