api_indexer_lookup_account_transactions
Get account transaction history
This record as markdown: /tools/goplausible-algorand-mcp/api-indexer-lookup-account-transactions.md
What api_indexer_lookup_account_transactions does on Algorand MCP
AI agents call api_indexer_lookup_account_transactions to retrieve information from Algorand MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why api_indexer_lookup_account_transactions is rated Low
This tool queries historical transaction data from the Algorand blockchain indexer. It retrieves information without side effects, matching the Read category definition. While the broader Algorand MCP server includes financial tools, this specific tool is a lookup/query operation with minimal risk if misused — an AI agent could retrieve transaction history but cannot modify balances, execute trades, or cause…
From the tool's definition Tool name includes 'lookup' and description states 'Get account transaction history' — both indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs api_indexer_lookup_account_transactions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Algorand MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For api_indexer_lookup_account_transactions, this is the rule to start with:
api_indexer_lookup_account_transactions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Algorand MCP, apply this rule, and every api_indexer_lookup_account_transactions call is checked against it from then on.
Questions about api_indexer_lookup_account_transactions
Get account transaction history. It is categorised as a Read tool in the Algorand MCP MCP Server, which means it retrieves data without modifying state.
Register the Algorand MCP server in PolicyLayer and add a rule for api_indexer_lookup_account_transactions: 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. Nothing to install.
api_indexer_lookup_account_transactions 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 api_indexer_lookup_account_transactions 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 api_indexer_lookup_account_transactions. 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.
api_indexer_lookup_account_transactions is provided by the Algorand MCP server (goplausible/algorand-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Algorand, and thousands of servers like it.
This server
Across the catalogue