AI agents call eth_get_nft_owner to retrieve information from PortalMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a blockchain query to retrieve NFT ownership information. It has no side effects—it does not create, modify, delete, or execute code. It simply reads and returns existing data. While it interacts with a financial system (Ethereum), the tool itself performs no financial operations (no transfers, payments, or value movements).
From the tool's definition Tool name 'eth_get_nft_owner' and description 'Get the current owner of an NFT' indicate a read-only query operation that retrieves ownership data from the blockchain without modifying state.
Attacks that exploit this kind of access
Get the current owner of an NFT. It is categorised as a Read tool in the PortalMCP MCP Server, which means it retrieves data without modifying state.
Register the Portal MCP server in PolicyLayer and add a rule for eth_get_nft_owner: 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 PortalMCP. Nothing to install.
eth_get_nft_owner 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 eth_get_nft_owner 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 eth_get_nft_owner. 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.
eth_get_nft_owner is provided by the Portal MCP server (portalfnd/portalmcp). 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 →