Critical Risk →

apiosk_wallet_delete

Delete a local wallet from the MCP keystore.

Part of the Apiosk server.

apiosk_wallet_delete can permanently delete data in Apiosk, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE APIOSK →

Free to start. No card required.

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

Without a policy, an AI agent could call apiosk_wallet_delete in a loop, permanently destroying resources in Apiosk. There is no undo for destructive operations. PolicyLayer 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "apiosk_wallet_delete"
  ]
}

See the full Apiosk policy for all 158 tools.

Get this rule live on your own Apiosk server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY APIOSK →

View all 158 tools →

These attack patterns abuse exactly the kind of access apiosk_wallet_delete gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so apiosk_wallet_delete only ever does what you allow.

SECURE APIOSK →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the apiosk_wallet_delete tool do? +

Delete a local wallet from the MCP keystore.. It is categorised as a Destructive tool in the Apiosk 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 apiosk_wallet_delete? +

Register the Apiosk MCP server in PolicyLayer and add a rule for apiosk_wallet_delete: 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 Apiosk. Nothing to install.

What risk level is apiosk_wallet_delete? +

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

Yes. Add a rate_limit block to the apiosk_wallet_delete 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 apiosk_wallet_delete completely? +

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

apiosk_wallet_delete is provided by the Apiosk MCP server (apiosk-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Apiosk tool call.

Deterministic rules across all 158 Apiosk tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.