308 tools. 101 can modify or destroy data without limits.
29 destructive tools with no built-in limits. Policy required.
Last updated:
Financial operations (identity_transfer, jingswap_deposit_sbtc, jingswap_deposit_stx) can move real money. An agent caught in a loop could drain accounts before anyone notices.
Destructive tools (credentials_delete, identity_unset_wallet, jingswap_cancel_cycle) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (bounty_create, credentials_set, credentials_unlock) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (alex_swap, arxiv_compile_digest, deploy_contract) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
identity_transfer:
rules:
- action: deny Financial tools should be explicitly enabled per use case, not open by default.
credentials_delete:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
bounty_create:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
alex_get_pool_info:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Aibtc server exposes 17 financial tools including identity_transfer, jingswap_deposit_sbtc, jingswap_deposit_stx. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. Intercept lets you block financial tools by default or set per-tool rate limits.
Yes. The Aibtc server exposes 12 destructive tools including credentials_delete, identity_unset_wallet, jingswap_cancel_cycle. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Aibtc server has 56 write tools including bounty_create, credentials_set, credentials_unlock. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
308 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 207 are read-only. 101 can modify, create, or delete data.
One line change. Instead of running the Aibtc server directly, prefix it with Intercept: intercept -c io-github-aibtcdev-mcp-server.yaml -- npx -y @@aibtc/mcp-server. Download a pre-built policy from policylayer.com/policies/io-github-aibtcdev-mcp-server and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.