get_pipeline

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp

Low RISK CLASS

Category Read

Parameters 70 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-dchub-mcp-server/get-pipeline.md

WHAT IT DOES

What get_pipeline does on Mcp Server

AI agents call get_pipeline 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
`limit`	integer	—	Max results to return (1-500; default varies by tool)
`offset`	integer	—	Pagination offset, 0-based (skip this many results)
`status`	string	—	Pipeline stage filter: announced, permitted, construction, or operational
`country`	string	—	ISO 3166-1 alpha-2 country code, e.g. US, DE, SG
`operator`	string	—	Operator/provider company name, e.g. Equinix, Digital Realty, AWS
`min_capacity_mw`	number	—	Minimum project power capacity filter in megawatts (MW), e.g. 50 for hyperscale
`expected_completion_before`	string	—	Only projects with expected commissioning before this ISO-8601 date (YYYY-MM-DD), e.g. 2027-01-01

Parameters from the server's own tool schema.

RISK

Why get_pipeline is rated Low

This is a pure data retrieval tool. It queries a database of data-center and infrastructure projects and returns results based on filtering parameters. There are no side effects, no data modifications, no code execution, and no financial transactions. The tool provides business intelligence for M&A, capacity planning, and market analysis.

From the tool's definition Tool retrieves forward-looking construction pipeline data (540+ projects, 369 GW) filtered by status, operator, country, capacity, and timeline.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_pipeline 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_pipeline, this is the rule to start with:

get_pipeline Allowed

get_pipeline is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_pipeline": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Server, apply this rule, and every get_pipeline call is checked against it from then on.

FAQ

Questions about get_pipeline

What does the get_pipeline tool do? +

Use when a user asks "what is being built / announced / permitted" in a market or by an operator — the forward-looking construction pipeline (540+ projects, 369 GW). Example: "What data centers are under construction in Northern Virginia and when do they come online?" — get_pipeline market=northern-virginia status=construction. Params: status one of "announced" | "permitted" | "construction" | "operational"; operator (e.g. "Equinix", "Digital Realty", "AWS"); country (ISO-2, e.g. "US", "DE"); min_capacity_mw (e.g. 50 to filter hyperscale); expected_completion_before (ISO date, e.g. "2027-01-01"); limit/offset for pagination. Returns: {projects:[{name, operator, capacity_mw, status, expected_commissioning, market_slug, country, lat, lon}], total, generated_at}. Do NOT use for already-operational facilities (use search_facilities) or for the M&A deal flow (use list_transactions). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.

What parameters does get_pipeline accept? +

get_pipeline accepts 7 parameters: limit, offset, status, country, operator, min_capacity_mw, expected_completion_before. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_pipeline? +

Register the Mcp Server MCP server in PolicyLayer and add a rule for get_pipeline: 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.

What risk level is get_pipeline? +

get_pipeline is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pipeline? +

Yes. Add a rate_limit block to the get_pipeline 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.

How do I block get_pipeline completely? +

Set action: deny in the PolicyLayer policy for get_pipeline. 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.

What MCP server provides get_pipeline? +

get_pipeline 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.

KEEP EXPLORING

More on Mcp Server, and thousands of servers like it.

This server

All 79 Mcp Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →