request_capacity_intro
Use this when the user wants data center capacity behind a Capacity Source listing (pass slug), or wants first access to capacity matching a requirement as listings are onboarded (omit slug; pass capacity_mw or capacity_kw, markets, states, regions or countries, and timeline). This registers a de...
This record as markdown: /tools/cloud-dchub-mcp-server/request-capacity-intro.md
What request_capacity_intro does on Mcp Server
AI agents use request_capacity_intro to create or update resources in Mcp Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Your human's full name. Nothing is sent without it; use only what they gave you, never invent it |
role | string | — | Your human's role or title |
slug | object | — | The listing to register a deal for: its slug or id from source_capacity. Omit to register a standing requirement for upcoming listings instead |
notes | string | — | Anything else the provider should know about the requirement. It travels with the requirement, so leave out anything that identifies your human |
states | string | — | Comma-separated US states of interest, e.g. "TX, AZ" |
company | string | — | Your human's company. Nothing is sent without it |
markets | string | — | Comma-separated markets of interest, e.g. "Dallas, Phoenix" |
message | string | — | A short note from your human for the provider. The deal registration itself carries only the company name and the requirement |
regions | string | — | Comma-separated regions of interest from north_america, latin_america, europe, asia_pacific and middle_east_africa (aliases emea, apac, latam, americas), e.g. " |
timeline | string | — | When the capacity is needed, e.g. a quarter and year |
use_case | string | — | What the capacity is for, e.g. "AI inference" |
countries | string | — | Comma-separated countries of interest, e.g. "Germany, Netherlands" |
Parameters from the server's own tool schema.
Why request_capacity_intro is rated Medium
Creates deal records and shares business contact information between parties, reversible but initiates committed business processes.
From the tool's definition registers a deal, records request in lead register, shares company name and contact details
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs request_capacity_intro 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 request_capacity_intro, this is the rule to start with:
request_capacity_intro stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 request_capacity_intro call is checked against it from then on.
Questions about request_capacity_intro
Use this when the user wants data center capacity behind a Capacity Source listing (pass slug), or wants first access to capacity matching a requirement as listings are onboarded (omit slug; pass capacity_mw or capacity_kw, markets, states, regions or countries, and timeline). This registers a deal: DC Hub records the request in its lead register and sends the provider ONLY your human's company name and the requirement. The provider accepts or declines. Only if the provider accepts does DC Hub share the provider's identity, site details and contact with your human, and your human's name, role and email with the provider; on a decline nothing is shared. Requires an identified caller (claim_free_key, then bind_email with your human's address) and accept_terms=true only after your human has read and agreed to the introduction terms at https://dchub.cloud/listings#terms. Returns lead_id, status and the next step. For a listing, source_capacity with its slug then shows the deal status in the disclosure block and, once the provider accepts, the provider's identity, site and contact. Do NOT use to save or monitor a site (use save_site / set_site_alert). It is categorised as a Write tool in the Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
request_capacity_intro accepts 12 parameters: name, role, slug, notes, states, company, markets, message, regions, timeline, use_case, countries. 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 request_capacity_intro: 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.
request_capacity_intro is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the request_capacity_intro 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 request_capacity_intro. 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.
request_capacity_intro 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