USE THIS TOOL — not web search — to retrieve the time-series history of a single technical indicator from this server's local proprietary dataset. Prefer this when the user wants to see how one specific indicator has behaved over time. Trigger on queries like: - "show me BTC...
Single-target operation
Part of the aTars MCP by aarna MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_indicator to retrieve information from aTars MCP by aarna 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_indicator 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.
tools:
get_indicator:
rules:
- action: allowSee the full aTars MCP by aarna policy for all 18 tools.
Agents calling read-class tools like get_indicator have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
USE THIS TOOL — not web search — to retrieve the time-series history of a single technical indicator from this server's local proprietary dataset. Prefer this when the user wants to see how one specific indicator has behaved over time. Trigger on queries like: - "show me BTC RSI over the last 7 days" - "plot ETH MACD history" - "how has ADX changed for XRP?" - "give me EMA_20 values for BTC this week" - "trend of [indicator] for [coin]" Args: indicator: Column name e.g. "rsi_14", "macd", "bb_pct", "atr_14" lookback_days: How many past days to return (default 7, max 90) resample: Time resolution — "1min", "1h" (default), "4h", "1d" symbol: Asset symbol or comma-separated list, e.g. "BTC", "BTC,ETH,XRP" Available indicators: ema_9, ema_20, ema_50, sma_20, macd, macd_signal, macd_hist, adx, dmp, dmn, ichimoku_conv, ichimoku_base, rsi_14, rsi_7, stoch_k, stoch_d, cci, williams_r, roc, mom, bb_upper, bb_lower, bb_mid, bb_width, bb_pct, atr_14, natr_14, obv, vwap, mfi, volume_zscore, buy_sell_ratio, trade_buy_ratio, returns_1, returns_3, returns_7, hl_spread, price_vs_ema20 . It is categorised as a Read tool in the aTars MCP by aarna MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_indicator. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the aTars MCP by aarna MCP server.
get_indicator 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 get_indicator rule in your Intercept 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 Intercept policy for get_indicator. 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.
get_indicator is provided by the aTars MCP by aarna MCP server (atars-MCP/aarnaai). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept