AI agents use strato.lending.borrow-max to commit financial operations through Griphook — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool initiates a maximum borrowing operation on a blockchain lending protocol. Borrowing crypto assets creates a financial liability (debt position) on-chain. 'Borrow max' specifically takes the largest possible loan, maximizing financial exposure. If misused by an AI agent, it could result in maximum debt obligations, liquidation risk, and irreversible financial commitments on the STRATO DeFi platform.
From the tool's definition 'Borrow the maximum available USDST' — borrows cryptocurrency (USDST) on a DeFi lending platform, committing a financial obligation
Attacks that exploit this kind of access
Borrow the maximum available USDST. 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.borrow-max: 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.borrow-max 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.borrow-max 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.borrow-max. 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.borrow-max 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 →