Deploys a new ERC721 (NFT) token to the specified network.
AI agents invoke deploy_erc721 to trigger actions in SEI MCP Server V2. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Deploying a token is an executable operation that triggers blockchain state changes and creates an irreversible on-chain artifact. While not strictly Destructive (it does not delete data), it is irreversible and commits the agent to deploying contract code to a live blockchain.
From the tool's definition deploy_erc721 deploys a new ERC721 (NFT) token to the specified network. This is an Execute action that triggers external operations on the blockchain whose effects depend on supplied arguments (network, token parameters).
Attacks that exploit this kind of access
Deploys a new ERC721 (NFT) token to the specified network. It is categorised as a Execute tool in the SEI MCP Server V2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for deploy_erc721: 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.
deploy_erc721 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deploy_erc721 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 deploy_erc721. 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.
deploy_erc721 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 →