Get transaction history for an account
AI agents call getAccountHistory 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 and returns historical transaction data associated with an account. It retrieves information without creating, modifying, deleting, or executing any operations. The read-only nature of transaction history lookup presents minimal risk—it is purely informational and has no blast radius if misused by an agent, as it cannot affect blockchain state or user assets.
From the tool's definition Tool name 'getAccountHistory' and description 'Get transaction history for an account' both indicate a retrieval operation with no side effects or modifications.
Attacks that exploit this kind of access
Get transaction history 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 getAccountHistory: 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.
getAccountHistory 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 getAccountHistory 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 getAccountHistory. 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.
getAccountHistory 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 →