Search transactions with optional filters (v2 endpoint).
AI agents call searchTransactionsV2 to retrieve information from Lofty 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 transaction data based on optional filter criteria but does not create, modify, delete, or execute external operations. It is a straightforward read operation with minimal blast radius—an AI agent misusing it could only access/exfiltrate existing transaction data without causing irreversible harm or financial movement.
From the tool's definition Tool name 'searchTransactionsV2' and description 'Search transactions with optional filters' indicate a query/search operation without modification or deletion. The verb 'search' combined with 'filters' describes data retrieval.
Attacks that exploit this kind of access
Search transactions with optional filters (v2 endpoint). It is categorised as a Read tool in the Lofty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for searchTransactionsV2: 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 Lofty MCP Server. Nothing to install.
searchTransactionsV2 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 searchTransactionsV2 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 searchTransactionsV2. 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.
searchTransactionsV2 is provided by the Lofty MCP Server MCP server (nerdsnipe-inc/lofty-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 →