signet_triggers
Open (or historical) Jupiter TRIGGER ORDERS placed from your Signet session accounts — limit orders, stop-losses and take-profits that Jupiter's keepers fill when the price condition is met. CALL THIS BEFORE PLACING ANOTHER ORDER: nothing in a run remembers an order (that is the point of handing ...
This record as markdown: /tools/ai-rokha-rokha/signet-triggers.md
What signet_triggers does on Rokha
AI agents call signet_triggers 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
status | string | — | 'active' (default) or 'history'. |
address | string | — | A specific session address. Omit to cover every session you own. |
Parameters from the server's own tool schema.
Why signet_triggers is rated Low
Tool only retrieves trigger order data; no modifications or financial transactions performed.
From the tool's definition Reads only; it cannot place or cancel
Attacks that exploit this kind of access
The rule that runs signet_triggers 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_triggers, this is the rule to start with:
signet_triggers 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_triggers call is checked against it from then on.
Questions about signet_triggers
Open (or historical) Jupiter TRIGGER ORDERS placed from your Signet session accounts — limit orders, stop-losses and take-profits that Jupiter's keepers fill when the price condition is met. CALL THIS BEFORE PLACING ANOTHER ORDER: nothing in a run remembers an order (that is the point of handing the waiting to Jupiter), so an agent that does not look will stack duplicates. status: 'active' (default) or 'history'. If an account cannot be read it is listed in unreadable and the result is flagged INCOMPLETE — never treat that as "no open orders". Reads only; it cannot place or cancel. Requires Authorization: Bearer <JWT>. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
signet_triggers accepts 2 parameters: status, address. 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_triggers: 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_triggers 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_triggers 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_triggers. 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_triggers 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