Sign a prepared sponsored mint transaction as the configured sponsor and broadcast it with the user
AI agents use submit_sponsored_mint to commit financial operations through Sui MCP SHIT Minter — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Minting tokens on a blockchain is a financial operation that creates new digital assets with potential monetary value. Broadcasting the transaction makes it irreversible once confirmed on-chain.
From the tool's definition 'Sign a prepared sponsored mint transaction as the configured sponsor and broadcast it' — mints tokens on a blockchain, committing financial operations (token creation/issuance) on the Sui blockchain
Attacks that exploit this kind of access
Sign a prepared sponsored mint transaction as the configured sponsor and broadcast it with the user. It is categorised as a Financial tool in the Sui MCP SHIT Minter MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Sui MCP SHIT Minter MCP server in PolicyLayer and add a rule for submit_sponsored_mint: 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 Sui MCP SHIT Minter. Nothing to install.
submit_sponsored_mint is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the submit_sponsored_mint 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 submit_sponsored_mint. 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.
submit_sponsored_mint is provided by the Sui MCP SHIT Minter MCP server (nomirizky55/shit-sui-mcp2). 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 →