bitflow_execute_token_swap_with_keeper

Execute token swap using Keeper system for automated execution

Server Stacks AI MCP Server stack-ai-mcp/stacks-mcp-server
Category Financial
Risk class Critical
Parameters 00 required

What bitflow_execute_token_swap_with_keeper does on Stacks AI MCP Server

AI agents use bitflow_execute_token_swap_with_keeper to commit financial operations through Stacks AI MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Why bitflow_execute_token_swap_with_keeper needs a policy

This tool executes token swaps on a DeFi protocol, which directly moves cryptocurrency assets between parties. Token swaps are financial transactions that commit on-chain asset transfers. The 'automated execution' via a Keeper system means it can trigger financial operations with minimal human intervention, amplifying the blast radius if misused.

From the tool's definition Execute token swap using Keeper system for automated execution

Questions about bitflow_execute_token_swap_with_keeper

What does the bitflow_execute_token_swap_with_keeper tool do? +

Execute token swap using Keeper system for automated execution. It is categorised as a Financial tool in the Stacks AI MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on bitflow_execute_token_swap_with_keeper? +

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

What risk level is bitflow_execute_token_swap_with_keeper? +

bitflow_execute_token_swap_with_keeper is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit bitflow_execute_token_swap_with_keeper? +

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

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

bitflow_execute_token_swap_with_keeper is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.