signet_paper_buy
PAPER. Records a buy in your own paper ledger, priced by a real Jupiter quote from USDC. No mandate, no signature, no funds. No quote = refused, never a made-up price. Pass one fill or buys: [...] (up to 20). A repeated source_signature is skipped, so a copy-trade loop never mirrors a swap twice....
This record as markdown: /tools/ai-rokha-rokha/signet-paper-buy.md
What signet_paper_buy does on Rokha
AI agents use signet_paper_buy 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 |
|---|---|---|---|
buys | array | — | Several fills of the fields above. |
mint | string | — | Full mint address, or SOL / USDC. |
ledger | string | — | Ledger name, a-z 0-9 '-', default 'default'. |
reason | string | — | |
symbol | string | — | |
amount_usd | number | — | USD to spend. |
amount_tokens | number | — | Or: tokens to buy. |
source_signature | string | — | The copied wallet's swap signature. |
Parameters from the server's own tool schema.
Why signet_paper_buy is rated Critical
Records financial transactions in a ledger using real market prices, simulating trades.
From the tool's definition Records a buy in your own paper ledger, priced by a real Jupiter quote
Attacks that exploit this kind of access
The rule that runs signet_paper_buy 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_buy, this is the rule to start with:
Any call to signet_paper_buy 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_buy call is checked against it from then on.
Questions about signet_paper_buy
PAPER. Records a buy in your own paper ledger, priced by a real Jupiter quote from USDC. No mandate, no signature, no funds. No quote = refused, never a made-up price. Pass one fill or buys: [...] (up to 20). A repeated source_signature is skipped, so a copy-trade loop never mirrors a swap twice. 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_buy accepts 8 parameters: buys, mint, ledger, reason, symbol, amount_usd, amount_tokens, source_signature. 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_buy: 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_buy 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_buy 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_buy. 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_buy 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