check_nft_ownership

Check if an address owns a specific NFT

SERVEREVM MCP Server SOURCEchulanpro5/evm-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/chulanpro5-evm-mcp-server/check-nft-ownership.md

WHAT IT DOES

What check_nft_ownership does on EVM MCP Server

AI agents call check_nft_ownership to retrieve information from EVM MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_nft_ownership is rated Low

This tool queries blockchain state to determine NFT ownership—a read operation with no side effects. It retrieves data but does not create, modify, delete, or execute transactions. The sibling tools show financial and destructive operations (buy_usdt_from_wallet, deploy_token, add_liquidity), making this tool's read-only nature clear by contrast. No blast radius from misuse beyond information disclosure.

From the tool's definition Tool name is 'check_nft_ownership' with description 'Check if an address owns a specific NFT'. The verb 'check' and 'owns' indicate a read-only query operation that retrieves ownership information without modifying state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_nft_ownership safely

PolicyLayer is an MCP gateway: it sits between your AI agents and EVM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_nft_ownership, this is the rule to start with:

check_nft_ownership Allowed

check_nft_ownership is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_nft_ownership": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EVM MCP Server, apply this rule, and every check_nft_ownership call is checked against it from then on.

FAQ

Questions about check_nft_ownership

What does the check_nft_ownership tool do? +

Check if an address owns a specific NFT. It is categorised as a Read tool in the EVM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_nft_ownership? +

Register the EVM MCP Server MCP server in PolicyLayer and add a rule for check_nft_ownership: 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 EVM MCP Server. Nothing to install.

What risk level is check_nft_ownership? +

check_nft_ownership is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_nft_ownership? +

Yes. Add a rate_limit block to the check_nft_ownership 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.

How do I block check_nft_ownership completely? +

Set action: deny in the PolicyLayer policy for check_nft_ownership. 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.

What MCP server provides check_nft_ownership? +

check_nft_ownership is provided by the EVM MCP Server MCP server (chulanpro5/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EVM MCP Server, and thousands of servers like it.

This server

All 36 EVM MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →