Get NEP-17 transfer history for an address with additive known-account enrichment when available
AI agents call get_nep17_transfers to retrieve information from Neo N3 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 blockchain transfer data for an address. It performs no writes, deletes, executions, or financial transactions—only queries existing ledger information. While the broader server manages wallets and assets, this specific tool is scoped to read-only access to transfer history, making it a Read category tool with low severity.
From the tool's definition Tool name 'get_nep17_transfers' and description 'Get NEP-17 transfer history for an address' indicate a retrieval operation. The phrase 'transfer history' and 'get' explicitly describe querying/reading data without modification.
Attacks that exploit this kind of access
Get NEP-17 transfer history for an address with additive known-account enrichment when available. It is categorised as a Read tool in the Neo N3 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Neo N3 MCP Server MCP server in PolicyLayer and add a rule for get_nep17_transfers: 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 Neo N3 MCP Server. Nothing to install.
get_nep17_transfers 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_nep17_transfers 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_nep17_transfers. 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_nep17_transfers is provided by the Neo N3 MCP Server MCP server (r3e-network/neo-n3-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 →