Get EVM transaction info with transaction hash on flowscan.io. flow EVM address is 20 bytes long, which is 40 characters long or 42 characters long with 0x prefix. NOTE: This is tool for flow EVM chain not flow blockchain.
AI agents call get_evm_transaction_info to retrieve information from Flow MCP 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 blockchain transaction data without any side effects, modification, execution, or financial impact. It is a straightforward informational lookup matching the Read category definition. The low severity reflects minimal blast radius—an AI agent misusing this tool can only access already-public blockchain data.
From the tool's definition Tool name 'get_evm_transaction_info' and description 'Get EVM transaction info' indicate retrieval of transaction information.
Attacks that exploit this kind of access
Get EVM transaction info with transaction hash on flowscan.io. flow EVM address is 20 bytes long, which is 40 characters long or 42 characters long with 0x prefix. NOTE: This is tool for flow EVM chain not flow blockchain. It is categorised as a Read tool in the Flow MCP MCP Server, which means it retrieves data without modifying state.
Register the Flow MCP server in PolicyLayer and add a rule for get_evm_transaction_info: 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. Nothing to install.
get_evm_transaction_info 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_evm_transaction_info 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_evm_transaction_info. 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_evm_transaction_info is provided by the Flow MCP server (outblock/flow-mcp-monorepo). 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 →