Get bias analysis for a specific article by its URL. Use this when you have a direct link to an article and want to know its political leaning, credibility, emotionality, and other bias dimensions — without needing to know the source name first. On success (found=true), returns: ...
Accepts URL/endpoint input (url); Single-target operation
Part of the Helium MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_bias_from_url 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 get_bias_from_url 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_bias_from_url:
rules:
- action: allowSee the full Helium policy for all 9 tools.
Agents calling read-class tools like get_bias_from_url 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.
Get bias analysis for a specific article by its URL. Use this when you have a direct link to an article and want to know its political leaning, credibility, emotionality, and other bias dimensions — without needing to know the source name first. On success (found=true), returns: - title, source, date, link, category - teaser: article excerpt - summary: one-sentence AI summary - context: AI-generated context for the article - bias_description: narrative description of this specific article's bias - bias_values: dict of per-dimension bias scores using plain-text keys (same schema as get_all_source_biases and search_news), e.g. {"liberal conservative bias": 12.3, "overall credibility": 40.1, "emotional bias": -5.2, ...} Positive values lean toward the second pole of each dimension (conservative, authoritarian, etc.). - total_shares: total social shares - wayback_link: Wayback Machine archive URL if available - image: article image URL if available On failure (found=false, HTTP 404): - found: false - message: explanation string The URL is automatically queued for ingestion; retry after ~24 hours. Tip: if you want source-level bias (not article-level), use get_source_bias instead. Tip: bias_values keys here use plain-text format (e.g. 'liberal conservative bias') and are identical to those in get_all_source_biases and search_news. Note: get_source_bias returns bias_scores with emoji-prefixed display keys — do not cross-reference them with bias_values here. Args: url: Full article URL, e.g. 'https://www.nytimes.com/2024/01/01/us/politics/example.html'. . 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 get_bias_from_url. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Helium MCP server.
get_bias_from_url 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_bias_from_url 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_bias_from_url. 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_bias_from_url 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