signet_action

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

Critical RISK CLASS

Category Financial

Parameters 73 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-action.md

WHAT IT DOES

What signet_action does on Rokha

AI agents use signet_action 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
`actor`	string	Yes	must match a mandate you granted
`chain`	integer	—
`value`	string	—	value moved, wei (for pay/transfer)
`target`	string	—	the contract/recipient (for pay/transfer/call)
`payload`	object	—	the action detail — deploy: {name, symbol}; pay: {to, amount}
`action_type`	string	Yes
`human_summary`	string	Yes	one line: exactly what this does

Parameters from the server's own tool schema.

RISK

Why signet_action is rated Critical

Executes real blockchain transactions transferring funds on Solana with no human approval required.

From the tool's definition SIGNS + SUBMITS on-chain, pay/transfer, lamports, SPL token

Risk signalsAccepts raw HTML/template content (payload)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs signet_action 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_action, this is the rule to start with:

signet_action Approval-gated

Any call to signet_action 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_action": {
      "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_action call is checked against it from then on.

FAQ

Questions about signet_action

What does the signet_action tool do? +

Step 3: DO it. Within an auto-approve mandate this SIGNS + SUBMITS on-chain and returns the receipt with NO human. SOLANA (chain 501, a mandate with a session_address): pay/transfer payload {to, amount} in base units (lamports), or {to, amount, mint} for an SPL token — the tx is simulated before signing and refuses honestly (target must be in the mandate's allowlist; value must equal amount; caps metered). On a plain wallet connection it returns an unsigned_tx for you to sign — then signet_submit. Over the mandate's limit it escalates to the owner. deploy payload: {name, symbol} → a real coin via the launch pad (EVM testing adapter). x402 (buy a paid HTTP resource): action_type 'x402', target = the resource URL, value = your USDC CEILING (base units) for this call — Signet does the 402 → pay → retry round trip, pays the exact price under your ceiling from the mandate's session wallet (Solana exact-scheme, USDC), and returns the resource; the unspent headroom is released. 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_action accept? +

signet_action accepts 7 parameters: actor, chain, value, target, payload, action_type, human_summary. Required: actor, action_type, human_summary. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on signet_action? +

Register the Rokha MCP server in PolicyLayer and add a rule for signet_action: 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_action? +

signet_action 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_action? +

Yes. Add a rate_limit block to the signet_action 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_action completely? +

Set action: deny in the PolicyLayer policy for signet_action. 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_action? +

signet_action 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 →