get_opensea_events_by_collection

Get a list of events for a collection.

Server SEI MCP Server V2 testinguser1111111/sei-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_opensea_events_by_collection does on SEI MCP Server V2

AI agents call get_opensea_events_by_collection 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.

Why get_opensea_events_by_collection needs a policy

This tool retrieves historical or current events (such as sales, listings, offers) associated with an NFT collection on OpenSea. It performs a read-only query operation with no side effects on blockchain state, user assets, or financial positions. The low severity reflects minimal blast radius if misused—an agent could only retrieve data that is already public.

From the tool's definition Tool name 'get_opensea_events_by_collection' and description 'Get a list of events for a collection' indicate retrieval/querying of existing data with no modification, deletion, or financial transactions.

Questions about get_opensea_events_by_collection

What does the get_opensea_events_by_collection tool do? +

Get a list of events for a collection. It is categorised as a Read tool in the SEI MCP Server V2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_opensea_events_by_collection? +

Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for get_opensea_events_by_collection: 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.

What risk level is get_opensea_events_by_collection? +

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

Can I rate-limit get_opensea_events_by_collection? +

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

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

get_opensea_events_by_collection 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.