Search for transactions with various filters
AI agents call searchTransactions 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 retrieves historical transaction information based on filtering criteria. It performs a read-only operation on the blockchain with no side effects, no code execution, and no financial consequences. The filtering capability does not change the severity classification as filters are query parameters, not actions that modify state or commit value transfers.
From the tool's definition Tool name 'searchTransactions' and description 'Search for transactions with various filters' indicate querying/retrieving transaction data without modification or execution of blockchain state changes.
Attacks that exploit this kind of access
Search for transactions with various filters. 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 searchTransactions: 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.
searchTransactions 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 searchTransactions 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 searchTransactions. 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.
searchTransactions 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 →