Compare Pendle and Spectra yield opportunities side-by-side on the same chain. Auto-matches markets by underlying asset to produce a head-to-head comparison. Essential for MetaVault curators who can allocate to either protocol. Shows: - Implied APY (fixed rate) comparison - LP APY comparison (rel...
Part of the Spectra server.
Free to start. No card required.
AI agents call compare_pendle_spectra 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 compare_pendle_spectra 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.
{
"version": "1",
"default": "deny",
"tools": {
"compare_pendle_spectra": {}
}
}See the full Spectra policy for all 25 tools.
These attack patterns abuse exactly the kind of access compare_pendle_spectra gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Compare Pendle and Spectra yield opportunities side-by-side on the same chain. Auto-matches markets by underlying asset to produce a head-to-head comparison. Essential for MetaVault curators who can allocate to either protocol. Shows: - Implied APY (fixed rate) comparison - LP APY comparison (relevant for MetaVault allocation) - Pool liquidity and TVL comparison - Variable rate comparison - Per-market winner analysis Only works on chains where both Spectra and Pendle are deployed: Ethereum, Optimism, BSC, Sonic, Base, Arbitrum Use list_pendle_markets for Pendle-only chain data. Use scan_opportunities for Spectra-native capital-aware ranking.. It is categorised as a Read tool in the Spectra MCP Server, which means it retrieves data without modifying state.
Register the Spectra MCP server in PolicyLayer and add a rule for compare_pendle_spectra: 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 Spectra. Nothing to install.
compare_pendle_spectra 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 compare_pendle_spectra 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 compare_pendle_spectra. 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.
compare_pendle_spectra is provided by the Spectra MCP server (spectra-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Spectra tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.