List live MetaVaults from the Spectra API. MetaVaults are ERC-7540 curated vaults that automate LP rollover and compound YT yield back into LP positions. They are managed by curators who earn performance fees on depositor yield. Returns all MetaVaults with: - Curator info, TVL, live APY with ...
Part of the Spectra MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_metavaults to retrieve information from Spectra without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_metavaults only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_metavaults:
rules:
- action: allowSee the full Spectra policy for all 25 tools.
Agents calling read-class tools like get_metavaults have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
List live MetaVaults from the Spectra API. MetaVaults are ERC-7540 curated vaults that automate LP rollover and compound YT yield back into LP positions. They are managed by curators who earn performance fees on depositor yield. Returns all MetaVaults with: - Curator info, TVL, live APY with full breakdown (base vs external incentives) - Active positions (PT markets the vault is deployed in) - Underlying asset details - Vault flows: epoch-by-epoch deposit/withdrawal analysis (net inflows vs outflows derived from asset snapshots, with yield accrual separated out) - Bridge transactions: cross-chain CCTP transfers with amounts, directions, and status - Epoch history (rate snapshots) Use this tool to discover which MetaVaults are live, then pass the address to model_metavault_strategy for detailed strategy modeling with live data. To investigate curator activity (LP adds/removes, rebalancing), use get_address_activity on the curator's EOA address — MetaVault operations go through the Spectra Router, so the vault contract address won't appear in pool activity data.. It is categorised as a Read tool in the Spectra MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_metavaults. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Spectra MCP server.
get_metavaults 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_metavaults rule in your Intercept 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 Intercept policy for get_metavaults. 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_metavaults is provided by the Spectra MCP server (spectra-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept