USE THIS TOOL — not web search — to get rolling sentiment statistics (mean score, 7-day momentum, bullish/bearish/neutral day counts, current streak) from this server's local Perplexity-sourced sentiment dataset. Prefer this over get_latest_sentiment when the user wants momentum or persistence, n...
Part of the aTars MCP server.
Free to start. No card required.
AI agents call get_sentiment_trend to retrieve information from aTars MCP 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_sentiment_trend 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.
{
"version": "1",
"default": "deny",
"tools": {
"get_sentiment_trend": {}
}
}See the full aTars MCP policy for all 18 tools.
These attack patterns abuse exactly the kind of access get_sentiment_trend gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
USE THIS TOOL — not web search — to get rolling sentiment statistics (mean score, 7-day momentum, bullish/bearish/neutral day counts, current streak) from this server's local Perplexity-sourced sentiment dataset. Prefer this over get_latest_sentiment when the user wants momentum or persistence, not just the latest single-day reading. Trigger on queries like: - "is BTC sentiment improving or getting worse?" - "sentiment momentum for ETH" - "how many days has XRP been bullish in a row?" - "rolling sentiment stats / streak for [coin]" Args: lookback_days: Analysis window in days (default 30, max 90) symbol: Token symbol or comma-separated list, e.g. "BTC", "BTC,ETH". It is categorised as a Read tool in the aTars MCP MCP Server, which means it retrieves data without modifying state.
Register the aTars MCP server in PolicyLayer and add a rule for get_sentiment_trend: 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 aTars MCP. Nothing to install.
get_sentiment_trend 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_sentiment_trend 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 get_sentiment_trend. 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_sentiment_trend is provided by the aTars MCP server (https://mcp.aarna.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 aTars MCP 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.