get_facility_risk_delta
Use when a user asks what has CHANGED in a facility's (or its market's) risk profile recently — "has this site gotten riskier lately?", "which way is this market moving?" — a temporal question static-trained models can't answer. Returns the REAL DCPI market-health delta (excess-power score change...
This record as markdown: /tools/cloud-dchub-mcp-server/get-facility-risk-delta.md
What get_facility_risk_delta does on Mcp Server
AI agents call get_facility_risk_delta 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 |
|---|---|---|---|
since | string | — | Look-back window, e.g. "7d" or "30d" (default 7d) |
market | string | — | Alternatively, a market name or slug (e.g. "northern-virginia") |
facility_id | string | — | A DC Hub facility id or canonical slug to resolve the market context |
Parameters from the server's own tool schema.
Why get_facility_risk_delta is rated Low
This tool queries and retrieves historical data comparing risk profiles across time windows. It performs read-only analysis of existing data (daily snapshots, market deltas) without creating, modifying, or destroying any data. No code execution, financial transactions, or irreversible actions are involved. Low severity reflects minimal blast radius: misuse returns analytical insights without side effects.
From the tool's definition Tool returns temporal deltas in DCPI market-health scores and risk profile changes ('excess-power score change', 'direction improving/worsening/flat'); explicitly performs queries/retrieval of historical data snapshots with no modification, creation,…
Attacks that exploit this kind of access
The rule that runs get_facility_risk_delta 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_facility_risk_delta, this is the rule to start with:
get_facility_risk_delta 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_facility_risk_delta call is checked against it from then on.
Questions about get_facility_risk_delta
Use when a user asks what has CHANGED in a facility's (or its market's) risk profile recently — "has this site gotten riskier lately?", "which way is this market moving?" — a temporal question static-trained models can't answer. Returns the REAL DCPI market-health delta (excess-power score change over the window, direction improving/worsening/flat) from DC Hub's history-preserving daily snapshots. INTEGRITY: only DCPI market-health has a short-term temporal series; the site-hazard dimensions (FEMA disaster / USGS seismic / NOAA climate / WRI water) are DECLARED static (they don't change week-to-week) with a pointer to the point-in-time tool — never a fabricated week-over-week delta; no snapshot history → coverage:unavailable. Params: facility_id (a discovered-facility id or slug) OR market (a market name/slug), since (e.g. "7d"/"30d", default 7d). Returns {facility, dcpi_market_health:{delta, now, direction, coverage}, static_dimensions{...}, summary}. For the current point-in-time risk (not the change) use get_composite_site_score / get_disaster_risk / get_climate_intel. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_facility_risk_delta accepts 3 parameters: since, market, facility_id. 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_facility_risk_delta: 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_facility_risk_delta 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_facility_risk_delta 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_facility_risk_delta. 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_facility_risk_delta 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