search_facilities
Use this when the user asks which data centers exist, or who operates in a city, state or country; filters: country, state, city, operator, MW range, tier or text. Returns name, operator, location, market, status and MW where disclosed; each row is flagged verified or unverified_directory_listing...
This record as markdown: /tools/cloud-dchub-mcp-server/search-facilities.md
What search_facilities does on Mcp Server
AI agents call search_facilities 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 |
|---|---|---|---|
city | string | — | City name to filter facilities, e.g. Ashburn, Dallas |
tier | integer | — | Uptime Institute tier filter (1-4) |
limit | integer | — | Max results to return (1-500; default varies by tool) |
query | string | — | Free-text search over facility name/operator/location (mapped to the backend `q` param), e.g. "hyperscale Ashburn" |
state | string | — | US state abbreviation or region, e.g. VA, TX |
offset | integer | — | Pagination offset, 0-based (skip this many results) |
country | string | — | ISO 3166-1 alpha-2 country code, e.g. US, GB, SG |
mpp_pay | boolean | — | Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has expli |
operator | string | — | Operator/provider company name, e.g. Equinix, Digital Realty |
mpp_credential | string | — | Per-call payment (Stripe MPP): the Shared Payment Token for challenges[0]; pays that challenge for this one call. Send it only with your human's explicit approv |
max_capacity_mw | number | — | Maximum power capacity filter in megawatts (MW) |
min_capacity_mw | number | — | Minimum power capacity filter in megawatts (MW) |
Parameters from the server's own tool schema.
Why search_facilities is rated Low
Retrieves facility data without modification or execution; pure information query with pagination.
From the tool's definition filters, returns name, operator, location, market, status; queries data; no side effects
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs search_facilities 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 search_facilities, this is the rule to start with:
search_facilities 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 search_facilities call is checked against it from then on.
Questions about search_facilities
Use this when the user asks which data centers exist, or who operates in a city, state or country; filters: country, state, city, operator, MW range, tier or text. Returns name, operator, location, market, status and MW where disclosed; each row is flagged verified or unverified_directory_listing. Free: names and locations; MW and specs need a paid key. Ex: "Equinix sites in Virginia over 10 MW." Start here for a facility slug. No match = empty data, not an error: broaden filters. limit 1-500 (free tier 25); page with offset. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
search_facilities accepts 12 parameters: city, tier, limit, query, state, offset, country, mpp_pay, operator, mpp_credential, max_capacity_mw, min_capacity_mw. 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 search_facilities: 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.
search_facilities 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_facilities 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 search_facilities. 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_facilities 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