get_facility
Full metadata for one facility — name, operator, address, lat/lon, power capacity (MW total/used), cooling type, fiber providers (count + carrier list), commissioning year, status, the DCPI verdict for its market, and peer facilities nearby. Try: get_facility id=equinix-dc1-ashburn — or get_facil...
This record as markdown: /tools/cloud-dchub-mcp-server/get-facility.md
What get_facility does on Mcp Server
AI agents call get_facility 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 |
|---|---|---|---|
id | object | — | Alias for facility_id — a facility id/slug from a prior search result |
name | string | — | Facility name as a fallback lookup when no id/slug is known, e.g. "QTS Ashburn" |
slug | string | — | Facility slug from a prior search result, e.g. digital-realty-iad8 |
facility_id | object | — | Facility id from a prior search_facilities/search result (numeric or string), e.g. equinix-dc1-ashburn |
include_power | boolean | — | Include power capacity detail (total/used MW) in the response (default true) |
include_nearby | boolean | — | Include peer facilities near this one in the response (default true) |
Parameters from the server's own tool schema.
Why get_facility is rated Low
This is a straightforward data retrieval operation that queries and returns facility information without any side effects. The tool only reads metadata; it does not create, modify, delete, or execute anything. The low severity reflects minimal blast radius—retrieving facility metadata poses no material risk even if misused by an AI agent.
From the tool's definition Tool retrieves 'full metadata for one facility' including name, operator, address, coordinates, power capacity, cooling type, fiber providers, commissioning year, status, DCPI verdict, and peer facilities.
Attacks that exploit this kind of access
The rule that runs get_facility 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, this is the rule to start with:
get_facility 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 call is checked against it from then on.
Questions about get_facility
Full metadata for one facility — name, operator, address, lat/lon, power capacity (MW total/used), cooling type, fiber providers (count + carrier list), commissioning year, status, the DCPI verdict for its market, and peer facilities nearby. Try: get_facility id=equinix-dc1-ashburn — or get_facility slug=digital-realty-iad8. Returns ONE facility in full; do NOT use to search or list many facilities (use search_facilities). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_facility accepts 6 parameters: id, name, slug, facility_id, include_power, include_nearby. 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: 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 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 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. 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 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