AI agents call strato.lending to retrieve information from Griphook without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves blockchain lending state and metrics without creating, modifying, deleting, or executing any transactions. While the server context involves DeFi operations that could be financial in nature, this specific tool only queries existing data about lending protocol state. No side effects or state changes are possible through fetch operations alone.
From the tool's definition Tool description explicitly states 'Fetch lending pools, loans, liquidity, collateral, liquidations, and safety module state' — all read-only query operations with verbs like 'Fetch' indicating data retrieval with no modification or execution.
Attacks that exploit this kind of access
Fetch lending pools, loans, liquidity, collateral, liquidations, and safety module state. It is categorised as a Read tool in the Griphook MCP Server, which means it retrieves data without modifying state.
Register the Griphook MCP server in PolicyLayer and add a rule for strato.lending: 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 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the strato.lending 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. 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 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 →