New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

signet_paper_reset

PAPER. Deletes one of your paper ledgers and every trade in it. Requires Authorization: Bearer <JWT>.

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc
Critical RISK CLASS
Category Destructive
Parameters 11 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/signet-paper-reset.md

What signet_paper_reset does on Rokha

AI agents call signet_paper_reset to permanently remove resources in Rokha, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
ledger string Yes

Parameters from the server's own tool schema.

Why signet_paper_reset is rated Critical

Irreversibly deletes ledgers and trades, causing permanent data loss without recovery option.

From the tool's definition Deletes one of your paper ledgers and every trade in it.

Risk signalsBulk/mass operation — affects multiple targets

Questions about signet_paper_reset

What does the signet_paper_reset tool do? +

PAPER. Deletes one of your paper ledgers and every trade in it. Requires Authorization: Bearer <JWT>. It is categorised as a Destructive tool in the Rokha MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does signet_paper_reset accept? +

signet_paper_reset accepts 1 parameter: ledger. Required: ledger. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on signet_paper_reset? +

Register the Rokha MCP server in PolicyLayer and add a rule for signet_paper_reset: 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.

What risk level is signet_paper_reset? +

signet_paper_reset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit signet_paper_reset? +

Yes. Add a rate_limit block to the signet_paper_reset 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.

How do I block signet_paper_reset completely? +

Set action: deny in the PolicyLayer policy for signet_paper_reset. 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.

What MCP server provides signet_paper_reset? +

signet_paper_reset 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Rokha's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.