Measure how much USD can be traded before moving price by X%. Reads V3 pool state (slot0, liquidity, tick boundaries) for MfT arb pools. Returns per-pool depth, health classification (deep/thin/dry), and max profitable trade size. READ-ONLY, no wallet needed.
AI agents call liquidity_depth to retrieve information from Baselings without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries blockchain data (Uniswap V3 pool liquidity metrics) to measure trading depth and health. It performs no writes, executions, deletions, or financial transactions. The explicit 'READ-ONLY' designation and absence of state modification confirm it belongs in the Read category with low severity, as misuse would only expose analytics rather than cause operational harm.
From the tool's definition Tool description explicitly states 'READ-ONLY, no wallet needed' and describes reading V3 pool state (slot0, liquidity, tick boundaries). The verbs used are 'Reads', 'Returns' — purely data retrieval operations with no side effects.
Attacks that exploit this kind of access
Measure how much USD can be traded before moving price by X%. Reads V3 pool state (slot0, liquidity, tick boundaries) for MfT arb pools. Returns per-pool depth, health classification (deep/thin/dry), and max profitable trade size. READ-ONLY, no wallet needed. It is categorised as a Read tool in the Baselings MCP Server, which means it retrieves data without modifying state.
Register the Baselings MCP server in PolicyLayer and add a rule for liquidity_depth: 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 Baselings. Nothing to install.
liquidity_depth 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 liquidity_depth 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 liquidity_depth. 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.
liquidity_depth is provided by the Baselings MCP server (jimbo530/baselings-mcp). 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 →