Search Helium's balanced news stories — AI-synthesized articles that aggregate multiple sources. Unlike search_news (which returns individual RSS articles), this returns Helium's own synthesized stories: each one draws from multiple sources and includes an AI-written summary, takeawa...
Accepts freeform code/query input (query)
Part of the Helium MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call search_balanced_news to retrieve information from Helium 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 search_balanced_news 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:
search_balanced_news:
rules:
- action: allowSee the full Helium policy for all 9 tools.
Agents calling read-class tools like search_balanced_news 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.
Search Helium's balanced news stories — AI-synthesized articles that aggregate multiple sources. Unlike search_news (which returns individual RSS articles), this returns Helium's own synthesized stories: each one draws from multiple sources and includes an AI-written summary, takeaway, context, evidence breakdown, potential outcomes, and relevant tickers. Returns a list of stories, each with: - title, simple_title, date, category - page_url: full URL to the story on heliumtrades.com - image: story image URL (when available) - summary: Helium's synthesized overview - takeaway: key conclusion - context: background context - evidence: numbered evidence items - potential_outcomes: forward-looking outcomes with probabilities - relevant_tickers: related stock tickers - num_sources: number of source articles synthesized - rank: search relevance score Args: query: Search keywords (required). limit: Max results (1-50, default 10). category: Filter by category. One of: 'tech', 'politics', 'markets', 'business', 'science'. days_back: Only include stories from the last N days. 0 means no date filter. . It is categorised as a Read tool in the Helium MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for search_balanced_news. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Helium MCP server.
search_balanced_news 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 search_balanced_news 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 search_balanced_news. 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.
search_balanced_news is provided by the Helium MCP server (conner-m4el/helium-mcp). 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