sap_chart_indicators
Compute technical indicators (RSI, EMA-20, EMA-50, MACD, Bollinger Bands, ATR) from DexScreener price data. Returns pre-calculated values with trend/momentum/volatility signals. Reduces analysis time by 5-10 tool calls. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: priced by...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-chart-indicators.md
What sap_chart_indicators does on Sap
AI agents call sap_chart_indicators 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). |
indicators | array | — | Indicators to compute. Default: all. |
resolution | string | — | Chart resolution for indicator calculation. |
Parameters from the server's own tool schema.
Why sap_chart_indicators is rated Low
Tool retrieves and calculates financial market data without modifying, executing code, or moving funds.
From the tool's definition Compute technical indicators from DexScreener price data. Returns pre-calculated values.
Attacks that exploit this kind of access
The rule that runs sap_chart_indicators 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_indicators, this is the rule to start with:
sap_chart_indicators 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_indicators call is checked against it from then on.
Questions about sap_chart_indicators
Compute technical indicators (RSI, EMA-20, EMA-50, MACD, Bollinger Bands, ATR) from DexScreener price data. Returns pre-calculated values with trend/momentum/volatility signals. Reduces analysis time by 5-10 tool calls. 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_indicators accepts 3 parameters: mint, indicators, resolution. 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_indicators: 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_indicators 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_indicators 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_indicators. 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_indicators 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