Submit a signed one-time relayer approval transaction.
AI agents invoke submit_relayer_approval to trigger actions in Sui MCP SHIT Minter. 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.
This tool submits a signed transaction to the Sui blockchain to approve a relayer, which is an on-chain operation with real effects. It triggers an external blockchain operation that grants permissions to a relayer entity.
From the tool's definition Submit a signed one-time relayer approval transaction
Attacks that exploit this kind of access
Submit a signed one-time relayer approval transaction. It is categorised as a Execute tool in the Sui MCP SHIT Minter MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sui MCP SHIT Minter MCP server in PolicyLayer and add a rule for submit_relayer_approval: 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_relayer_approval 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 submit_relayer_approval 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_relayer_approval. 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_relayer_approval 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 →