# 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).

Agent View of the PolicyLayer registry record for `request_capacity_intro`. HTML page: https://policylayer.com/tools/cloud-dchub-mcp-server/request-capacity-intro

## Facts

- Tool: `request_capacity_intro`
- Server: Mcp Server (`https://dchub.cloud/mcp`) — https://policylayer.com/tools/cloud-dchub-mcp-server.md
- Homepage: https://github.com/azmartone67/dchub-mcp-server
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 12
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no | Your human's full name. Nothing is sent without it; use only what they gave you, never invent it |
| `role` | string | no | Your human's role or title |
| `slug` | object | no | 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 | no | Anything else the provider should know about the requirement. It travels with the requirement, so leave out anything that identifies your human |
| `states` | string | no | Comma-separated US states of interest, e.g. "TX, AZ" |
| `company` | string | no | Your human's company. Nothing is sent without it |
| `markets` | string | no | Comma-separated markets of interest, e.g. "Dallas, Phoenix" |
| `message` | string | no | A short note from your human for the provider. The deal registration itself carries only the company name and the requirement |
| `regions` | string | no | 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 | no | When the capacity is needed, e.g. a quarter and year |
| `use_case` | string | no | What the capacity is for, e.g. "AI inference" |
| `countries` | string | no | Comma-separated countries of interest, e.g. "Germany, Netherlands" |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "request_capacity_intro",
    "arguments": {}
  }
}
```

## 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 own definition: "registers a deal, records request in lead register, shares company name and contact details"

Risk signals: High parameter count (16 properties)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_capacity_intro": {
      "limits": [
        {
          "counter": "request_capacity_intro_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp Server (93)

- `delete_standing_intent` — Destructive — https://policylayer.com/tools/cloud-dchub-mcp-server/delete-standing-intent.md
- `suggest_reallocation` — Destructive — https://policylayer.com/tools/cloud-dchub-mcp-server/suggest-reallocation.md
- `execute_plan` — Execute — https://policylayer.com/tools/cloud-dchub-mcp-server/execute-plan.md
- `simulate_scenario` — Execute — https://policylayer.com/tools/cloud-dchub-mcp-server/simulate-scenario.md
- `unlock_more_data` — Financial — https://policylayer.com/tools/cloud-dchub-mcp-server/unlock-more-data.md
- `accept_capacity_terms` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/accept-capacity-terms.md
- `ai_capacity_index` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/ai-capacity-index.md
- `analyze_parcel` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/analyze-parcel.md
- `analyze_site` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/analyze-site.md
- `bind_email` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/bind-email.md
- `cluster_sites_by_latency` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/cluster-sites-by-latency.md
- `compare_isos` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/compare-isos.md
- `compare_sites` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/compare-sites.md
- `deal_autopsy` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/deal-autopsy.md
- `discover_tools` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/discover-tools.md
- `fetch` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/fetch.md
- `find_alternatives` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/find-alternatives.md
- `find_sites` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/find-sites.md
- `get_agent_registry` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/get-agent-registry.md
- `get_backup_status` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/get-backup-status.md
- `get_changes` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/get-changes.md
- `get_climate_intel` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/get-climate-intel.md
- `get_composite_site_score` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/get-composite-site-score.md
- `get_dchub_recommendation` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/get-dchub-recommendation.md
- `get_disaster_risk` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/get-disaster-risk.md
- `get_energy_prices` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/get-energy-prices.md
- `get_facility` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/get-facility.md
- `get_facility_risk_delta` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/get-facility-risk-delta.md
- `get_fiber_intel` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/get-fiber-intel.md
- `get_fiber_readiness` — Read — https://policylayer.com/tools/cloud-dchub-mcp-server/get-fiber-readiness.md
- …and 63 more: https://policylayer.com/tools/cloud-dchub-mcp-server.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=cloud-dchub-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/cloud-dchub-mcp-server