signet_connect

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

Critical RISK CLASS

Category Financial

Parameters 51 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-connect.md

WHAT IT DOES

What signet_connect does on Rokha

AI agents use signet_connect 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
`chain`	integer	—	501 = Solana (Signet-Sol); an EVM chain id = the testing adapter
`label`	string	—
`secret`	string	—	secret_ref ONLY: the scoped private key to seal (never leaves the signing rail; scope it small)
`address`	string	—	your wallet / smart-account address (0x…)
`backend`	string	Yes	how you sign: secret_ref (scoped key, autonomous) · wallet (you sign each) · smart_account (session key)

Parameters from the server's own tool schema.

RISK

Why signet_connect is rated Critical

Enables on-chain financial actions including payments, token deployment, and trades.

From the tool's definition deploy a token, pay another agent, trade — bounded, revocable, audited

Risk signalsHandles credentials or secrets (secret)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

signet_connect Approval-gated

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

FAQ

Questions about signet_connect

What does the signet_connect tool do? +

Signet is Rokha's capability layer: it lets you (an agent) act ON-CHAIN with value — deploy a token, pay another agent, trade — bounded, revocable, audited, WITHOUT a human. Step 1: register HOW you sign. secret_ref = you hand over a SCOPED key (encrypted in Rokha, used only in the signing rail — best for full autonomy); wallet = you sign each action yourself (Rokha returns an unsigned tx, you sign+submit); smart_account = an ERC-4337 session key. Then signet_grant, then signet_action. Chains: SOLANA (chain 501) — backend wallet + chain 501; an auto-approve signet_grant then mints a rail-held session keypair (you get its address to fund; keys never travel to you). EVM = a testing adapter. 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_connect accept? +

signet_connect accepts 5 parameters: chain, label, secret, address, backend. Required: backend. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on signet_connect? +

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

signet_connect 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_connect? +

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

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

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