fetch
Fetch a DC Hub record for an id returned by the search tool (OpenAI Deep Research / ChatGPT connector format). Returns {id, title, text, url, metadata} — a citable public summary of one data-center facility (name, operator, location, status, market). For full structured specs (capacity MW, coordi...
This record as markdown: /tools/cloud-dchub-mcp-server/fetch.md
What fetch does on Mcp Server
AI agents call fetch 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 |
|---|---|---|---|
id | string | Yes | A facility id/slug from a prior `search` result, e.g. equinix-dc1-ashburn |
Parameters from the server's own tool schema.
Why fetch is rated Low
This tool retrieves and queries existing data about data-center facilities without any capacity to modify, delete, or execute operations. It is a read-only lookup mechanism that returns summary information already accessible via public data sources. The low severity reflects minimal blast radius—misuse would only retrieve facility information that appears to be publicly available intelligence.
From the tool's definition Tool description states it 'Fetch[es] a DC Hub record' and 'Returns {id, title, text, url, metadata} — a citable public summary of one data-center facility (name, operator, location, status, market).' It explicitly directs users to other tools for structural…
Attacks that exploit this kind of access
The rule that runs fetch 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 fetch, this is the rule to start with:
fetch 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 fetch call is checked against it from then on.
Questions about fetch
Fetch a DC Hub record for an id returned by the search tool (OpenAI Deep Research / ChatGPT connector format). Returns {id, title, text, url, metadata} — a citable public summary of one data-center facility (name, operator, location, status, market). For full structured specs (capacity MW, coordinates) use get_facility or open the url. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
fetch accepts 1 parameter: id. Required: id. 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 fetch: 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.
fetch 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 fetch 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 fetch. 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.
fetch 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