sap_chart_long_term
Fetch long-term price history for a Solana token from DexScreener and optional protocol TVL data from DeFiLlama. Returns price changes, volume, liquidity, FDV, and TVL history. Read-only — uses free REST APIs. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: priced by hosted x4...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-chart-long-term.md
What sap_chart_long_term does on Sap
AI agents call sap_chart_long_term to retrieve information from Sap without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
mint | string | Yes | Token mint address (base58) for price history. |
protocol | string | — | Optional DeFiLlama protocol slug for TVL history (e.g. "jupiter", "raydium"). |
Parameters from the server's own tool schema.
Why sap_chart_long_term is rated Low
Tool queries public price and TVL data with no side effects or data modification.
From the tool's definition Fetch long-term price history, read-only, uses free REST APIs.
Attacks that exploit this kind of access
The rule that runs sap_chart_long_term safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sap_chart_long_term, this is the rule to start with:
sap_chart_long_term is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_chart_long_term call is checked against it from then on.
Questions about sap_chart_long_term
Fetch long-term price history for a Solana token from DexScreener and optional protocol TVL data from DeFiLlama. Returns price changes, volume, liquidity, FDV, and TVL history. Read-only — uses free REST APIs. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: priced by hosted x402 challenge. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. It is categorised as a Read tool in the Sap MCP Server, which means it retrieves data without modifying state.
sap_chart_long_term accepts 2 parameters: mint, protocol. Required: mint. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for sap_chart_long_term: 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 Sap. Nothing to install.
sap_chart_long_term 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 sap_chart_long_term 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 sap_chart_long_term. 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.
sap_chart_long_term is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sap, and thousands of servers like it.
This server
Across the catalogue