Get NFTs owned by a given account address on the Sei chain.
AI agents call get_opensea_nfts_by_account to retrieve information from SEI MCP Server V2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves NFT ownership information from the OpenSea marketplace on the Sei blockchain. It performs a read-only operation with no side effects, no code execution, no financial transactions, and no data modification. The only risk is information disclosure of public blockchain data, which is minimal.
From the tool's definition Tool name and description explicitly indicate a 'Get' operation: 'Get NFTs owned by a given account address'. This retrieves data without modifying or executing state changes.
Attacks that exploit this kind of access
Get NFTs owned by a given account address on the Sei chain. It is categorised as a Read tool in the SEI MCP Server V2 MCP Server, which means it retrieves data without modifying state.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for get_opensea_nfts_by_account: 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 SEI MCP Server V2. Nothing to install.
get_opensea_nfts_by_account 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_opensea_nfts_by_account 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_opensea_nfts_by_account. 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_opensea_nfts_by_account is provided by the SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). 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 →