Add single-sided liquidity to a Pendle market and receive LP tokens
AI agents use add_liquidity to create or update resources in Waiaas — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Waiaas environment.
The tool modifies the user's asset holdings by committing capital to a Pendle liquidity pool. While this is reversible (unlike a destructive operation) and doesn't move money to external parties (unlike Financial category which requires transfers between parties), it creates a financial obligation and position.
From the tool's definition Tool performs 'Add single-sided liquidity' which creates/modifies financial positions and receives LP tokens in return. This is a reversible state change (liquidity can be removed), but commits capital to a DeFi protocol with real financial consequences.
Documented attack patterns abuse exactly the kind of access add_liquidity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Waiaas, and nothing reaches the server without passing your rules. This is the rule we recommend for add_liquidity:
{
"version": "1",
"default": "deny",
"tools": {
"add_liquidity": {
"limits": [
{
"counter": "add_liquidity_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_liquidity 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.
Free to start. No card required.
Add single-sided liquidity to a Pendle market and receive LP tokens. It is categorised as a Write tool in the Waiaas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Waiaas MCP server in PolicyLayer and add a rule for 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 Waiaas. Nothing to install.
add_liquidity 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 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 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.
add_liquidity is provided by the Waiaas MCP server (minhoyoo-iotrust/waiaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Waiaas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
126 Waiaas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.