Get NEP-11 transfer history for an address with additive asset and party enrichment when available
AI agents call get_nep11_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 transfer data for NEP-11 tokens (NFT standard on Neo N3) associated with a blockchain address. The verb 'Get' and the passive nature of querying transfer history with enrichment indicate a read-only operation with no side effects.
From the tool's definition Tool name 'get_nep11_transfers' and description 'Get NEP-11 transfer history for an address' indicate a query/retrieval operation with 'additive asset and party enrichment when available' suggesting data enhancement without mutation.
Attacks that exploit this kind of access
Get NEP-11 transfer history for an address with additive asset and party 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_nep11_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_nep11_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_nep11_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_nep11_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_nep11_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 →