signet_submit

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Critical RISK CLASS

Category Financial

Parameters 22 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/signet-submit.md

WHAT IT DOES

What signet_submit does on Rokha

AI agents use signet_submit to commit financial operations through Rokha, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`tx_hash`	string	Yes	the 0x…64 hash of the tx you broadcast
`request_id`	string	Yes	from signet_action

Parameters from the server's own tool schema.

RISK

Why signet_submit is rated Critical

Submits signed blockchain transactions, irreversibly committing financial operations on-chain.

From the tool's definition signed + broadcast the unsigned_tx, tx_hash, token/pool

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs signet_submit safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For signet_submit, this is the rule to start with:

signet_submit Approval-gated

Any call to signet_submit is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "signet_submit": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every signet_submit call is checked against it from then on.

FAQ

Questions about signet_submit

What does the signet_submit tool do? +

Only for wallet-backend actions: after you signed + broadcast the unsigned_tx from signet_action, hand back the tx_hash. Rokha confirms the receipt and returns the result (token/pool/links). Requires Authorization: Bearer <JWT>. It is categorised as a Financial tool in the Rokha MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does signet_submit accept? +

signet_submit accepts 2 parameters: tx_hash, request_id. Required: tx_hash, request_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on signet_submit? +

Register the Rokha MCP server in PolicyLayer and add a rule for signet_submit: 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 Rokha. Nothing to install.

What risk level is signet_submit? +

signet_submit is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit signet_submit? +

Yes. Add a rate_limit block to the signet_submit 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.

How do I block signet_submit completely? +

Set action: deny in the PolicyLayer policy for signet_submit. 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.

What MCP server provides signet_submit? +

signet_submit is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →