Low Risk

get_pt_details

Get detailed information about a specific Spectra Principal Token (PT). Returns: maturity date, TVL, implied APY, PT/YT prices, pool liquidity, LP APY breakdown, underlying asset info, IBT protocol, yield leverage, pool reserves (IBT/PT amounts), maturity redemption value, points program multipli...

Part of the Spectra server.

get_pt_details is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE SPECTRA →

Free to start. No card required.

AI agents call get_pt_details 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_pt_details 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_pt_details": {}
  }
}

See the full Spectra policy for all 25 tools.

Get this rule live on your own Spectra server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SPECTRA →

View all 25 tools →

These attack patterns abuse exactly the kind of access get_pt_details gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_pt_details only ever does what you allow.

SECURE SPECTRA →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_pt_details tool do? +

Get detailed information about a specific Spectra Principal Token (PT). Returns: maturity date, TVL, implied APY, PT/YT prices, pool liquidity, LP APY breakdown, underlying asset info, IBT protocol, yield leverage, pool reserves (IBT/PT amounts), maturity redemption value, points program multipliers, asset tags, and base IBT info. Protocol context: - PT trades at a discount to its underlying (the discount IS the fixed yield). At maturity, PT redeems for the maturityValue shown (may differ from 1:1). - PT + YT = 1 underlying at maturity. YT price = 1 - PT price (in underlying terms). - YT leverage shows how much yield exposure 1 unit of YT provides relative to holding the underlying directly. Higher leverage = more amplified yield exposure. - IBT APR breakdown shows organic yield vs external incentive programs. High APR from incentives alone may not be sustainable. Use compare_yield to compare fixed vs. variable rates. Use get_looping_strategy to calculate leveraged fixed yield via Morpho. Use get_portfolio to check wallet holdings. Use get_pool_activity to see trading patterns on this pool.. It is categorised as a Read tool in the Spectra MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pt_details? +

Register the Spectra MCP server in PolicyLayer and add a rule for get_pt_details: 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.

What risk level is get_pt_details? +

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

Can I rate-limit get_pt_details? +

Yes. Add a rate_limit block to the get_pt_details 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_pt_details completely? +

Set action: deny in the PolicyLayer policy for get_pt_details. 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_pt_details? +

get_pt_details 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.

Enforce policy on every Spectra tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.