Get transaction details by ID
AI agents call get_transaction to retrieve information from Flow 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 and queries transaction information from the Flow blockchain. It has no side effects—it does not create, modify, delete, or execute operations. It is purely a data retrieval operation, fitting the Read category. The severity is low because reading transaction data poses minimal risk; it only exposes existing information without enabling harmful actions.
From the tool's definition The tool is named 'get_transaction' and described as 'Get transaction details by ID'. The verb 'Get' and the read-only nature of retrieving transaction details indicate this retrieves data without modification.
Attacks that exploit this kind of access
Get transaction details by ID. It is categorised as a Read tool in the Flow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Flow MCP Server MCP server in PolicyLayer and add a rule for get_transaction: 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 Flow MCP Server. Nothing to install.
get_transaction 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 get_transaction 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 get_transaction. 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.
get_transaction is provided by the Flow MCP Server MCP server (lmcmz/flow-mcp-server). 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 →