Add liquidity to existing Arkadiko swap pair
AI agents use arkadiko_add_liquidity 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.
Adding liquidity to a DeFi swap pair involves transferring cryptocurrency assets into a smart contract. This is a financial operation that commits real value, is not trivially reversible (requires a separate remove-liquidity transaction, subject to impermanent loss and fees), and directly affects the user's financial position.
From the tool's definition 'Add liquidity to existing Arkadiko swap pair' — commits real assets (tokens) to a DeFi liquidity pool on-chain
Attacks that exploit this kind of access
Add liquidity to existing Arkadiko swap pair. 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 arkadiko_add_liquidity: 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.
arkadiko_add_liquidity 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 arkadiko_add_liquidity 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 arkadiko_add_liquidity. 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.
arkadiko_add_liquidity 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 →