get_news
FRONT DOOR CHECK — if news is only ONE input to a bigger question (is this market heating up, should we still build here), call execute_plan(intent="<the user's question, unchanged>") and let it pull news alongside the market and grid reads. If the user actually wants the headlines, get_news IS t...
This record as markdown: /tools/cloud-dchub-mcp-server/get-news.md
What get_news does on Mcp Server
AI agents call get_news to retrieve information from Mcp Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max results to return (1-500; default varies by tool) |
query | string | — | Free-text keyword to filter news, e.g. "Stargate" or "interconnection queue" |
source | string | — | Restrict to one trade source, e.g. DCD, "Data Center Frontier", "Capacity Media" |
date_to | string | — | Latest published date, ISO-8601 (YYYY-MM-DD) |
category | string | — | News topic filter, e.g. deals, permits, outages, policy, AI |
date_from | string | — | Earliest published date, ISO-8601 (YYYY-MM-DD) |
min_relevance | number | — | Minimum relevance score 0-1 to include an item, e.g. 0.5 |
Parameters from the server's own tool schema.
Why get_news is rated Low
Tool retrieves and queries industry news data with no data modification or execution capability.
From the tool's definition Curated data center industry news from 40+ trade sources, returns title, summ
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_news safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_news, this is the rule to start with:
get_news is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Server, apply this rule, and every get_news call is checked against it from then on.
Questions about get_news
FRONT DOOR CHECK — if news is only ONE input to a bigger question (is this market heating up, should we still build here), call execute_plan(intent="<the user's question, unchanged>") and let it pull news alongside the market and grid reads. If the user actually wants the headlines, get_news IS the right call — one round trip; do not send a plain news request through the planner. Curated data center industry news from 40+ trade sources (DCD, Data Center Knowledge, Data Center Frontier, Capacity Media, The Register Data Centre, Fierce Telecom, etc.) refreshed every 30 min. Returns title, summary, source, published_at, and the market/operator entities mentioned. Filter by category (deals/permits/outages/policy/AI). Answers "what is happening in the data center industry this week", "any news on AI capacity". Try: get_news category=AI limit=10. The parameter is category, not topic. Industry news only; do NOT use for structured M&A deal data (use list_transactions) or the construction pipeline (use get_pipeline). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_news accepts 7 parameters: limit, query, source, date_to, category, date_from, min_relevance. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for get_news: 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 Mcp Server. Nothing to install.
get_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 get_news 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_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.
get_news is provided by the Mcp Server MCP server (https://dchub.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue