signet_status
Everything you've set up in Signet: your signer connections, active mandates (with spend used vs cap + expiry + the session_address to fund), and recent actions with their results. Requires Authorization: Bearer <JWT>.
This record as markdown: /tools/ai-rokha-rokha/signet-status.md
What signet_status does on Rokha
AI agents call signet_status to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why signet_status is rated Low
Tool queries configuration and transaction status without creating, modifying, or deleting data.
From the tool's definition Retrieve signer connections, mandates, session data, recent actions without modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs signet_status 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_status, this is the rule to start with:
signet_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every signet_status call is checked against it from then on.
Questions about signet_status
Everything you've set up in Signet: your signer connections, active mandates (with spend used vs cap + expiry + the session_address to fund), and recent actions with their results. Requires Authorization: Bearer <JWT>. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
Register the Rokha MCP server in PolicyLayer and add a rule for signet_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 Rokha. Nothing to install.
signet_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 signet_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 signet_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.
signet_status 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.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue