source_capacity
Use this when the user needs data center or colocation capacity to buy or lease: search DC Hub Capacity Source by size (kW or MW) and/or location (a region such as North America or Europe, a country, a state or a metro). Example: "500 kW anywhere in Europe" → min_kw=500, region=europe. Size is mi...
This record as markdown: /tools/cloud-dchub-mcp-server/source-capacity.md
What source_capacity does on Mcp Server
AI agents call source_capacity 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 |
|---|---|---|---|
slug | object | — | One listing: its slug or numeric id exactly as items[].slug / items[].id return it. Omit to browse teaser cards |
limit | integer | — | Max results to return (1-500; default varies by tool) |
state | string | — | Browse filter: two-letter US state, e.g. "TX" |
market | string | — | Browse filter: market name as it appears on a listing, e.g. "Dallas" |
min_kw | number | — | Browse filter: the size your human needs, in kW (min_mw is the same filter in MW). Matched against what a listing can ACTUALLY deliver, not just its headline to |
min_mw | number | — | Browse filter: the size your human needs, in MW (min_kw is the same filter in kW). Matched against what a listing can ACTUALLY deliver, not just its headline to |
region | string | — | Browse filter: comma-separated regions from north_america, latin_america, europe, asia_pacific and middle_east_africa; the aliases emea, apac, latam and america |
location | string | — | Browse filter: comma-separated free text matched against each listing's region, country, state and metro, e.g. "Germany" or "Texas, Phoenix" |
max_sites | integer | — | Match mode: how many listings the requirement may be split across. Default one, which allows exact fits only; raise it to allow bundles |
target_kw | number | — | Match mode: the whole requirement, in kW (target_mw is the same in MW; give one) |
target_mw | number | — | Match mode: the whole requirement, in MW (target_kw is the same in kW; give one). Returns exact fits, bundles and a shortfall instead of teaser cards. Needs a s |
available_by | string | — | Browse filter: only listings available by this date, as YYYY-MM or YYYY-MM-DD. With a target it is the date the whole requirement must be deliverable by |
Parameters from the server's own tool schema.
Why source_capacity is rated Low
Queries capacity listings; returns matching results without modifying, deleting, or executing operations.
From the tool's definition search DC Hub Capacity Source by size and location; data center capacity query
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs source_capacity 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 source_capacity, this is the rule to start with:
source_capacity 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 source_capacity call is checked against it from then on.
Questions about source_capacity
Use this when the user needs data center or colocation capacity to buy or lease: search DC Hub Capacity Source by size (kW or MW) and/or location (a region such as North America or Europe, a country, a state or a metro). Example: "500 kW anywhere in Europe" → min_kw=500, region=europe. Size is min_kw (in kW) or min_mw (in MW), and it is matched against what a listing can ACTUALLY deliver rather than against its headline total: contiguous_kw is the largest single contiguous block available and min_contract_kw the smallest chunk the provider will contract, so a colocation with a large total but a small contiguous block does NOT answer a large search, while a large site willing to contract small chunks does; a listing that declares neither is matched on its total. Location is region (a region key or alias) or location (free text matched against each listing's region, country, state and metro); market, state, delivery_type and available_by narrow further. Listings are powered land, powered shells, turnkey capacity and colocation to buy or lease, for enterprise and agent-led procurement. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
source_capacity accepts 12 parameters: slug, limit, state, market, min_kw, min_mw, region, location, max_sites, target_kw, target_mw, available_by. 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 source_capacity: 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.
source_capacity 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 source_capacity 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 source_capacity. 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.
source_capacity 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