Drain remaining funds from a deployment wallet back to the treasury. NOTE: drain runs automatically inside printr_launch_token — only call this tool manually to recover a stuck wallet (e.g. after a crash or if printr_launch_token was not called). Automatically calculates gas fees and drains the m...
Part of the Printr MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke printr_drain_deployment_wallet to trigger processes or run actions in Printr. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
printr_drain_deployment_wallet can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
printr_drain_deployment_wallet:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Printr policy for all 25 tools.
Agents calling execute-class tools like printr_drain_deployment_wallet have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
printr_drain_deployment_wallet is one of the high-risk operations in Printr. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Drain remaining funds from a deployment wallet back to the treasury. NOTE: drain runs automatically inside printr_launch_token — only call this tool manually to recover a stuck wallet (e.g. after a crash or if printr_launch_token was not called). Automatically calculates gas fees and drains the maximum possible amount. Can recover wallets after MCP restart using persisted state and PRINTR_DEPLOYMENT_PASSWORD.. It is categorised as a Execute tool in the Printr MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for printr_drain_deployment_wallet. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Printr MCP server.
printr_drain_deployment_wallet is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the printr_drain_deployment_wallet 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.
Set action: deny in the Intercept policy for printr_drain_deployment_wallet. 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.
printr_drain_deployment_wallet 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.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.