AI agents use strato.lending.withdraw-liquidity to commit financial operations through Griphook — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Withdrawing liquidity from a lending pool is a financial transaction that moves assets. In a DeFi context, this directly affects the agent's (or user's) financial position and is irreversible on-chain. The server description explicitly mentions 'handling lending operations' as a core capability, confirming the financial nature of this tool.
From the tool's definition 'Withdraw from lending pool' — moves funds out of a DeFi lending pool, committing a financial operation on the blockchain.
Attacks that exploit this kind of access
Withdraw from lending pool. 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.lending.withdraw-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 Griphook. Nothing to install.
strato.lending.withdraw-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 strato.lending.withdraw-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 strato.lending.withdraw-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.
strato.lending.withdraw-liquidity 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 →