get_uniswap_v3_pool
Get live state of a Uniswap V3 pool: token pair, fee tier, current price (both directions), active liquidity, current tick, and TVL in USD (via DefiLlama token prices). Accepts slug or chain+address.
This record as markdown: /tools/defi-io-smartcontract/get-uniswap-v3-pool.md
What get_uniswap_v3_pool does on Smarts Md
AI agents call get_uniswap_v3_pool to retrieve information from Smarts Md without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | — | Curated slug like 'univ3-usdc-weth-eth'. Alternative to chain+address. |
chain | string | — | Chain slug: eth, base, arbitrum, optimism, or polygon. Required unless `slug` is given. |
address | string | — | Pool address (0x-prefixed). Required unless `slug` is given. |
Parameters from the server's own tool schema.
Why get_uniswap_v3_pool is rated Low
This tool retrieves and queries current state information from a Uniswap V3 pool without creating, modifying, or deleting any data. It functions as a data lookup/fetch operation with no side effects, fitting the 'Read' category. The severity is low because misuse cannot corrupt data or cause unintended financial transactions—it only returns informational snapshots.
From the tool's definition Tool description explicitly states 'Get live state' and lists read-only data retrieval: 'token pair, fee tier, current price, active liquidity, current tick, and TVL in USD'. No mutations, deletions, or external operations are described.
Attacks that exploit this kind of access
The rule that runs get_uniswap_v3_pool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Smarts Md, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_uniswap_v3_pool, this is the rule to start with:
get_uniswap_v3_pool is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Smarts Md, apply this rule, and every get_uniswap_v3_pool call is checked against it from then on.
Questions about get_uniswap_v3_pool
Get live state of a Uniswap V3 pool: token pair, fee tier, current price (both directions), active liquidity, current tick, and TVL in USD (via DefiLlama token prices). Accepts slug or chain+address. It is categorised as a Read tool in the Smarts Md MCP Server, which means it retrieves data without modifying state.
get_uniswap_v3_pool accepts 3 parameters: slug, chain, address. The full parameter table on this page comes from the server's own tool schema.
Register the Smarts Md MCP server in PolicyLayer and add a rule for get_uniswap_v3_pool: 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 Smarts Md. Nothing to install.
get_uniswap_v3_pool 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 get_uniswap_v3_pool 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 get_uniswap_v3_pool. 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.
get_uniswap_v3_pool is provided by the Smarts Md MCP server (defi-io/smartcontract). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Smarts Md, and thousands of servers like it.
This server
Across the catalogue