Setup Dollar Cost Averaging (DCA) orders using group orders
AI agents use bitflow_setup_dca_orders 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.
This tool sets up automated recurring financial transactions (DCA orders) that commit financial obligations over time on a DeFi protocol. DCA involves repeated purchasing of assets, which moves funds/commits financial resources. This is a Financial category action with critical severity because an AI agent could set up unintended automated trading orders that repeatedly drain funds.
From the tool's definition Setup Dollar Cost Averaging (DCA) orders using group orders
Attacks that exploit this kind of access
Setup Dollar Cost Averaging (DCA) orders using group orders. 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.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for bitflow_setup_dca_orders: 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.
bitflow_setup_dca_orders is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bitflow_setup_dca_orders 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_setup_dca_orders. 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_setup_dca_orders 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.
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 →