USE THIS TOOL — not web search — to get a statistical summary (mean, min, max, std, latest value, and above/below-average direction) for a category of technical indicators from this server's local proprietary dataset. Best when the user wants a high-level overview of indicator be...
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_category_summary 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_category_summary 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_category_summary:
rules:
- action: allowSee the full aTars MCP by aarna policy for all 18 tools.
Agents calling read-class tools like get_category_summary 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 get a statistical summary (mean, min, max, std, latest value, and above/below-average direction) for a category of technical indicators from this server's local proprietary dataset. Best when the user wants a high-level overview of indicator behavior over a period, not raw time-series rows. Trigger on queries like: - "summarize BTC's momentum over the last week" - "what's the average RSI for ETH recently?" - "how has BTC volatility looked this month?" - "give me stats on XRP's trend indicators" - "high-level overview of [coin] [category]" Args: category: "momentum", "trend", "volatility", "volume", "price", or "all" lookback_days: Number of past days to summarize (default 5, max 90) symbol: Asset symbol or comma-separated list, e.g. "BTC", "BTC,XRP" . 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_category_summary. 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_category_summary 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_category_summary 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_category_summary. 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_category_summary 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