Low Risk

get_owners

Get all addresses owning a specific NFT, multitoken, or ERC-20.

How to control get_owners ↓

AI agents call get_owners to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries blockchain state to retrieve owner information. It reads data without side effects, matching the Read category definition. The severity is low because retrieving public blockchain data poses minimal risk even if misused by an AI agent—it cannot modify state, execute transactions, or cause harm. The high confidence reflects the clear read-only nature of the operation.

From the tool's definition Tool description states 'Get all addresses owning a specific NFT, multitoken, or ERC-20' — a retrieval operation with no modification, deletion, or execution of code/transactions.

Documented attack patterns abuse exactly the kind of access get_owners gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_owners:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_owners": {}
  }
}

get_owners is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register BNB Chain MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_owners tool do? +

Get all addresses owning a specific NFT, multitoken, or ERC-20. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_owners? +

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

What risk level is get_owners? +

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

Can I rate-limit get_owners? +

Yes. Add a rate_limit block to the get_owners 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 get_owners completely? +

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

get_owners is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BNB Chain MCP tool call.

Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.