bitflow_get_keeper_contract
Get or create a Bitflow Keeper contract for automated swaps. Keeper contracts enable scheduled/automated token swaps. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/bitflow-get-keeper-contract.md
What bitflow_get_keeper_contract does on Aibtc
AI agents use bitflow_get_keeper_contract to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why bitflow_get_keeper_contract is rated Medium
The tool can create a Keeper contract on-chain (Write), which sets up infrastructure for automated swaps. While it has a 'get' aspect, the creation of a smart contract is a write operation. It doesn't directly move funds itself, but establishing automated swap contracts carries medium severity due to the potential for misuse in setting up unwanted automated trading infrastructure.
From the tool's definition Get or create a Bitflow Keeper contract for automated swaps. Keeper contracts enable scheduled/automated token swaps.
Attacks that exploit this kind of access
The rule that runs bitflow_get_keeper_contract 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 bitflow_get_keeper_contract, this is the rule to start with:
bitflow_get_keeper_contract stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every bitflow_get_keeper_contract call is checked against it from then on.
Questions about bitflow_get_keeper_contract
Get or create a Bitflow Keeper contract for automated swaps. Keeper contracts enable scheduled/automated token swaps. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aibtc MCP server in PolicyLayer and add a rule for bitflow_get_keeper_contract: 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.
bitflow_get_keeper_contract is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bitflow_get_keeper_contract 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.
Set action: deny in the PolicyLayer policy for bitflow_get_keeper_contract. 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.
bitflow_get_keeper_contract 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.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue