delete_hiro_api_key

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.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/delete-hiro-api-key.md

WHAT IT DOES

What delete_hiro_api_key does on Aibtc

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

RISK

Why delete_hiro_api_key is rated Critical

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_hiro_api_key safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_hiro_api_key, this is the rule to start with:

delete_hiro_api_key Hidden

delete_hiro_api_key is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every delete_hiro_api_key call is checked against it from then on.

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.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 369 Aibtc tools → Critical-risk tools on this server →

Across the catalogue

delete_ssh_key on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →web3_revoke_key on 0xarchive → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →