fetch-transactions
AI agents call fetch-transactions to retrieve information from Lineage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and context of sibling read-only blockchain query tools strongly suggest fetch-transactions retrieves transaction data without modification. However, the empty description and potential for this tool to expose sensitive transaction history (revealing wallet activity, transaction patterns, financial behavior) warrant medium severity classification despite being a Read operation.
From the tool's definition Tool name 'fetch-transactions' indicates data retrieval. Server description states it provides tools to 'query' blockchain data including 'balance queries' and 'latest block retrieval.' The sibling tools (fetch-balance, get-balance, get-block-by-number,…
Attacks that exploit this kind of access
fetch-transactions. It is categorised as a Read tool in the Lineage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lineage MCP Server MCP server in PolicyLayer and add a rule for fetch-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 Lineage MCP Server. Nothing to install.
fetch-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 fetch-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 fetch-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.
fetch-transactions is provided by the Lineage MCP Server MCP server (lineage-foundation/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
fetch-transactions is one line of Lineage MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →