signet_paper_positions
PAPER. Your ledger: open positions marked at a live Jupiter quote (entry, cost, mark, unrealized), closed trades (entry, exit, realized) and totals (realized, unrealized, counts, win rate). Requires Authorization: Bearer <JWT>.
This record as markdown: /tools/ai-rokha-rokha/signet-paper-positions.md
What signet_paper_positions does on Rokha
AI agents use signet_paper_positions 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 |
|---|---|---|---|
ledger | string | — |
Parameters from the server's own tool schema.
Why signet_paper_positions is rated Critical
Tracks financial positions and trade history with live market data; financial in nature.
From the tool's definition open positions, closed trades, realized, unrealized, win rate
Attacks that exploit this kind of access
The rule that runs signet_paper_positions 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_paper_positions, this is the rule to start with:
Any call to signet_paper_positions is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every signet_paper_positions call is checked against it from then on.
Questions about signet_paper_positions
PAPER. Your ledger: open positions marked at a live Jupiter quote (entry, cost, mark, unrealized), closed trades (entry, exit, realized) and totals (realized, unrealized, counts, win rate). 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.
signet_paper_positions accepts 1 parameter: ledger. 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_paper_positions: 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_paper_positions is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the signet_paper_positions 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_paper_positions. 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_paper_positions 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