New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_curve_positions

READ-ONLY — Curve LP positions on Ethereum stable_ng plain pools. v0.1 scope (per claude-work/plan-curve-v1.md): Ethereum mainnet only, stable_ng factory only, plain pools only (meta pools rejected — different ABI, separate follow-up). Returns per-pool LP token balance + gauge-staked balance + pe...

SERVERVaultPilot MCP SOURCEvaultpilot-mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-curve-positions.md

What get_curve_positions does on VaultPilot MCP

AI agents call get_curve_positions to retrieve information from VaultPilot MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
wallet string Yes 0x EVM wallet address. v0.1 only reads Ethereum stable_ng plain pools — Arbitrum / Polygon and other factory variants land in follow-up PRs.

Parameters from the server's own tool schema.

Why get_curve_positions is rated Low

This tool retrieves and displays blockchain state information (LP token balances and pending rewards) without any side effects. It performs data querying only, matching the 'Read' category definition. Severity is low because misuse reveals only the user's existing portfolio composition and reward amounts, with no financial movement or execution risk.

From the tool's definition Tool is explicitly labeled 'READ-ONLY' and described as querying 'Curve LP positions on Ethereum stable_ng plain pools'.

Questions about get_curve_positions

What does the get_curve_positions tool do? +

READ-ONLY — Curve LP positions on Ethereum stable_ng plain pools. v0.1 scope (per claude-work/plan-curve-v1.md): Ethereum mainnet only, stable_ng factory only, plain pools only (meta pools rejected — different ABI, separate follow-up). Returns per-pool LP token balance + gauge-staked balance + pending claimable CRV. Pools where the wallet has zero of all three are filtered out. Future PRs add: legacy pre-factory pools (3pool, fraxusdc, etc.), stable factory v1, twocrypto/crypto/tricrypto factories, Arbitrum + Polygon. The tool surface stays additive — get_curve_positions will keep its name and shape across the expansion. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does get_curve_positions accept? +

get_curve_positions accepts 1 parameter: wallet. Required: wallet. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_curve_positions? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for get_curve_positions: 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 VaultPilot MCP. Nothing to install.

What risk level is get_curve_positions? +

get_curve_positions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_curve_positions? +

Yes. Add a rate_limit block to the get_curve_positions 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.

How do I block get_curve_positions completely? +

Set action: deny in the PolicyLayer policy for get_curve_positions. 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.

What MCP server provides get_curve_positions? +

get_curve_positions is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on VaultPilot, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of VaultPilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.