AI agents call list_vaults to retrieve information from Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
chainId | integer | — | Defaults to mainnet (1). |
Parameters from the server's own tool schema.
This tool only queries and returns public blockchain data (vault addresses and token pairs). It performs no state changes, executes no transactions, and accesses no private user information. It is a straightforward data retrieval operation with no side effects, fitting squarely within the Read category. The low severity reflects minimal risk—an AI agent cannot misuse public market data to cause harm.
From the tool's definition Description states 'List the public any-token LP vaults' and explicitly clarifies 'Public market data only — no user-private reads.' The tool retrieves vault addresses and token pair information without modification or execution of transactions.
Attacks that exploit this kind of access
List the public any-token LP vaults (addresses + token pair). Public market data only — no user-private reads. It is categorised as a Read tool in the Agent MCP Server, which means it retrieves data without modifying state.
list_vaults accepts 1 parameter: chainId. The full parameter table on this page comes from the server's own tool schema.
Register the Agent MCP server in PolicyLayer and add a rule for list_vaults: 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 Agent. Nothing to install.
list_vaults 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 list_vaults 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 list_vaults. 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.
list_vaults is provided by the Agent MCP server (https://fluxiq.xyz/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_vaults is one line of Agent's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →