Critical Risk

printr_wallet_bulk_remove

Remove multiple wallets from the local keystore at once. Does not affect active wallets for the current session.

Part of the Printr MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@printr/mcp Destructive Risk 4/5

AI agents may call printr_wallet_bulk_remove to permanently remove or destroy resources in Printr. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call printr_wallet_bulk_remove in a loop, permanently destroying resources in Printr. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-printrfi-printr.yaml
tools:
  printr_wallet_bulk_remove:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Printr policy for all 23 tools.

Tool Name printr_wallet_bulk_remove
Category Destructive
MCP Server Printr MCP Server
Risk Level Critical

View all 23 tools →

What does the printr_wallet_bulk_remove tool do? +

Remove multiple wallets from the local keystore at once. Does not affect active wallets for the current session.. It is categorised as a Destructive tool in the Printr MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on printr_wallet_bulk_remove? +

Add a rule in your Intercept YAML policy under the tools section for printr_wallet_bulk_remove. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Printr MCP server.

What risk level is printr_wallet_bulk_remove? +

printr_wallet_bulk_remove 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 printr_wallet_bulk_remove? +

Yes. Add a rate_limit block to the printr_wallet_bulk_remove rule in your Intercept 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 printr_wallet_bulk_remove completely? +

Set action: deny in the Intercept policy for printr_wallet_bulk_remove. 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 printr_wallet_bulk_remove? +

printr_wallet_bulk_remove is provided by the Printr MCP server (@printr/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Printr

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.