getPositionDetails
Gets detailed information about a specific Uniswap V3 LP position including token pair, fee tier, tick range, liquidity, and owed fees.
This record as markdown: /tools/nanidao-agentek/getpositiondetails.md
What getPositionDetails does on Agentek Eth
AI agents call getPositionDetails to retrieve information from Agentek Eth without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getPositionDetails is rated Low
This tool performs read-only queries on existing Uniswap V3 liquidity pool positions. It gathers position metadata and financial metrics without creating, modifying, deleting, or executing any state-changing operations. The information retrieved is informational for research and monitoring purposes, making it a classic Read category tool with minimal blast radius if misused.
From the tool's definition Tool retrieves 'detailed information about a specific Uniswap V3 LP position' including 'token pair, fee tier, tick range, liquidity, and owed fees' — all data queries with no modification or execution of transactions.
Attacks that exploit this kind of access
The rule that runs getPositionDetails safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentek Eth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getPositionDetails, this is the rule to start with:
getPositionDetails 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 Agentek Eth, apply this rule, and every getPositionDetails call is checked against it from then on.
Questions about getPositionDetails
Gets detailed information about a specific Uniswap V3 LP position including token pair, fee tier, tick range, liquidity, and owed fees. It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for getPositionDetails: 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 Agentek Eth. Nothing to install.
getPositionDetails 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 getPositionDetails 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 getPositionDetails. 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.
getPositionDetails is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentek Eth, and thousands of servers like it.
This server
Across the catalogue