Check configured Sui package, treasury cap, and shared mint config objects.
AI agents call check_mint_status to retrieve information from Sui MCP SHIT Minter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and validates the state of blockchain configuration objects. It performs no writes, executions, or financial transactions. The read-only nature and lack of side effects places it clearly in the Read category. Severity is low as unauthorized reads of public blockchain configuration data pose minimal risk.
From the tool's definition Tool description states it "Check[s] configured Sui package, treasury cap, and shared mint config objects" - purely a query/inspection operation with no modification or execution.
Attacks that exploit this kind of access
Check configured Sui package, treasury cap, and shared mint config objects. It is categorised as a Read tool in the Sui MCP SHIT Minter MCP Server, which means it retrieves data without modifying state.
Register the Sui MCP SHIT Minter MCP server in PolicyLayer and add a rule for check_mint_status: 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.
check_mint_status 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 check_mint_status 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 check_mint_status. 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.
check_mint_status 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 →