AI agents use strato.swap.add-liquidity-single to commit financial operations through Griphook — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Adding liquidity to a swap pool is a financial operation: it moves tokens from the user's wallet into a DeFi liquidity pool. This is irreversible in the sense that liquidity provision involves financial risk (impermanent loss, smart contract risk) and commits real assets, placing it firmly in the Financial category, which is the most severe applicable here.
From the tool's definition "Provide liquidity using only one token" — adding liquidity to a DeFi pool commits financial assets to a smart contract, constituting a financial obligation/commitment.
Attacks that exploit this kind of access
Provide liquidity using only one token. It is categorised as a Financial tool in the Griphook MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Griphook MCP server in PolicyLayer and add a rule for strato.swap.add-liquidity-single: 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 Griphook. Nothing to install.
strato.swap.add-liquidity-single 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 strato.swap.add-liquidity-single 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 strato.swap.add-liquidity-single. 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.
strato.swap.add-liquidity-single is provided by the Griphook MCP server (strato-net/strato-griphook). 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 →