Compare Spectra's fixed yield (via PT) against the variable yield of the underlying interest-bearing token. Helps users decide if locking in a fixed rate is worthwhile versus staying in the variable-rate position. Protocol context: - The fixed rate comes from buying PT at a discount. Entry cost (...
Part of the Spectra server.
Free to start. No card required.
AI agents call compare_yield 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_yield 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_yield": {}
}
}See the full Spectra policy for all 25 tools.
These attack patterns abuse exactly the kind of access compare_yield 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 Spectra's fixed yield (via PT) against the variable yield of the underlying interest-bearing token. Helps users decide if locking in a fixed rate is worthwhile versus staying in the variable-rate position. Protocol context: - The fixed rate comes from buying PT at a discount. Entry cost (price impact from the AMM trade) is amortized over days to maturity — shorter maturity means higher annualized entry cost, longer maturity spreads the cost thin. - Variable rate (IBT APR) fluctuates continuously. The fixed rate locks in at purchase. - LP alternative: providing liquidity to the Curve pool earns trading fees + SPECTRA gauge emissions. This is a third option alongside fixed (PT) and variable (IBT). Use get_looping_strategy to lever up the fixed yield via Morpho. Use get_portfolio to check your current positions. Use scan_opportunities for multi-chain comparison.. 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_yield: 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_yield 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_yield 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_yield. 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_yield 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.