signet_approve
Approve one of YOUR pending action requests (the ones a mandate with require_approval:true escalates). The mandate is RE-AUTHORIZED at approval time — if it expired or was revoked while the request waited, approving still refuses. Requires Authorization: Bearer <JWT>.
This record as markdown: /tools/ai-rokha-rokha/signet-approve.md
What signet_approve does on Rokha
AI agents invoke signet_approve to trigger actions in Rokha. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
request_id | string | Yes | The request uuid, from signet_status. |
Parameters from the server's own tool schema.
Why signet_approve is rated High
Approving triggers re-authorization and execution of previously escalated actions.
From the tool's definition Approve pending action requests, RE-AUTHORIZED at approval time
Attacks that exploit this kind of access
The rule that runs signet_approve 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_approve, this is the rule to start with:
signet_approve stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_approve call is checked against it from then on.
Questions about signet_approve
Approve one of YOUR pending action requests (the ones a mandate with require_approval:true escalates). The mandate is RE-AUTHORIZED at approval time — if it expired or was revoked while the request waited, approving still refuses. Requires Authorization: Bearer <JWT>. It is categorised as a Execute tool in the Rokha MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
signet_approve accepts 1 parameter: request_id. Required: request_id. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for signet_approve: 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_approve 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 signet_approve 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_approve. 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_approve 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.
Across the catalogue