delete_hiro_api_key

THE RISK

Critical Risk

Why delete_hiro_api_key needs a policy

This tool permanently deletes stored credentials from a configuration file. While the fallback to HIRO_API_KEY environment variable limits some impact, the primary action is irreversible deletion of user-managed authentication material. This is more severe than Write (reversible modification) and qualifies as Destructive.

From the tool's definition Tool name is 'delete_hiro_api_key' and description states 'Remove the stored Hiro API key from ~/.aibtc/config.json'. The verb 'Remove' combined with deletion of persistent configuration data indicates irreversible data destruction.

Documented attack patterns abuse exactly the kind of access delete_hiro_api_key gives an agent:

POLICY

How to control delete_hiro_api_key

PolicyLayer is an MCP gateway — it sits between your AI agents and Aibtc, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_hiro_api_key:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_hiro_api_key"
  ]
}

delete_hiro_api_key disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Aibtc — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Aibtc tools

Financial jingswap_cancel_stx Cancel your token-B deposit (STX or USDCx depending on market) from the current Jingswap a Financial ordinals_cancel_listing Cancel an active Magic Eden listing for an inscription. Requests a cancellation PSBT from Financial alex_swap Execute a token swap on ALEX DEX. Swaps tokenX for tokenY using the ALEX AMM. Use full co Financial bitflow_swap Execute a token swap on Bitflow DEX. Swaps tokenX for tokenY using Bitflow Financial dual_stacking_enroll Enroll in Dual Stacking to earn sBTC rewards. Enrolls your wallet in the Dual Stacking pr Financial execute_x402_endpoint Execute an x402 API endpoint. Payment is handled automatically. Supported sources: - x402 Financial news_file_signal File a signal on a beat at aibtc.news. Requires an unlocked wallet with a P2WPKH (bc1q) B Financial yield_hunter_start Start autonomous yield hunting. This will: 1. Monitor your wallet for sBTC 2. Automatical

All 353 Aibtc tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Govern code and CI agents → Branch allowlists, approval on merges, and rate caps on the build and pipeline tools agents trigger.
Critical-risk tools in Aibtc → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about delete_hiro_api_key

What does the delete_hiro_api_key tool do? +

Remove the stored Hiro API key from ~/.aibtc/config.json. If HIRO_API_KEY is set in the environment, that will still be used as a fallback. It is categorised as a Destructive tool in the Aibtc 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 delete_hiro_api_key? +

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

What risk level is delete_hiro_api_key? +

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

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

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

delete_hiro_api_key is provided by the Aibtc MCP server (aibtcdev/aibtc-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 Aibtc tool call.

Start from Aibtc, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →