Prepare an unsigned Sui transaction that pays 1 SUI and mints 10M SHIT to the user
AI agents use prepare_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.
This tool prepares a transaction that involves a financial commitment — paying 1 SUI (a cryptocurrency with real monetary value) in exchange for minting tokens. Although it only 'prepares' an unsigned transaction (so the funds aren't moved yet), it is directly part of a financial flow involving real crypto assets. The most severe applicable category is Financial due to the SUI payment involved.
From the tool's definition pays 1 SUI and mints 10M SHIT to the user
Attacks that exploit this kind of access
Prepare an unsigned Sui transaction that pays 1 SUI and mints 10M SHIT to 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 prepare_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.
prepare_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 prepare_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 prepare_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.
prepare_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 →