Critical Risk

credentials_delete

Remove a stored credential by service and key. The encrypted store file is rewritten without the deleted entry.

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

@aibtc/mcp-server Destructive Risk 4/5

AI agents may call credentials_delete to permanently remove or destroy resources in Aibtc. 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 credentials_delete in a loop, permanently destroying resources in Aibtc. 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-aibtcdev-mcp-server.yaml
tools:
  credentials_delete:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Aibtc policy for all 288 tools.

Tool Name credentials_delete
Category Destructive
MCP Server Aibtc MCP Server
Risk Level Critical

View all 288 tools →

What does the credentials_delete tool do? +

Remove a stored credential by service and key. The encrypted store file is rewritten without the deleted entry.. 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 credentials_delete? +

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

What risk level is credentials_delete? +

credentials_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 credentials_delete? +

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

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

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

Enforce policies on Aibtc

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.