get_fiber_intel

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp

Low RISK CLASS

Category Read

Parameters 40 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-fiber-intel.md

WHAT IT DOES

What get_fiber_intel does on Mcp Server

AI agents call get_fiber_intel 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
`market`	string	—	Metro name or slug (e.g. "dallas", "ashburn", "northern-virginia") — returns only routes touching that metro (either endpoint within ~1.2°). Great with route_ty
`carrier`	string	—	Fiber carrier to filter on, e.g. Zayo, Lumen, Cogent, "Crown Castle", Windstream, GTT, Uniti; omit for all carriers
`route_type`	string	—	Route class: "metro", "longhaul", "dark", or "ix"
`include_sources`	boolean	—	Include upstream data-source/provenance metadata in the response

Parameters from the server's own tool schema.

RISK

Why get_fiber_intel is rated Low

This tool queries and retrieves geospatial and infrastructure intelligence data about fiber networks. It returns information for analysis and mapping purposes without creating, modifying, or deleting data, and without executing code or triggering operations.

From the tool's definition Tool retrieves fiber infrastructure data: 'Show all Zayo long-haul fiber routes', 'mapping long-haul routes', 'assessing dark-fiber availability', 'get_fiber_intel'. Parameters allow querying by carrier, route_type, and market.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_fiber_intel Allowed

get_fiber_intel 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_fiber_intel": {}
  }
}

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_fiber_intel call is checked against it from then on.

FAQ

Questions about get_fiber_intel

What does the get_fiber_intel tool do? +

Use when scoring a candidate site for fiber depth, mapping long-haul routes between metros, or assessing dark-fiber availability for a hyperscale build. Example: "Show all Zayo long-haul fiber routes through Northern Virginia I can put on a Leaflet map." — get_fiber_intel carrier=Zayo route_type=longhaul. Params: carrier one of "Zayo" | "Lumen" | "Cogent" | "Crown Castle" | "Windstream" | "GTT" | "Uniti" | "FiberLight" | "Segra" | "Arcadian Infracom" (omit for all carriers); route_type one of "metro" | "longhaul" | "dark" | "ix"; market a metro name or slug (e.g. "dallas", "ashburn", "northern-virginia") to return ONLY routes touching that metro (either endpoint near it) — pairs well with route_type=longhaul to map a metro's long-haul backbones. Returns: GeoJSON FeatureCollection {features:[{geometry, properties:{carrier, route_type, fiber_count, lit_capacity_gbps, capacity, distance_miles, distance_km}}]} ready to drop into Leaflet/Mapbox. Do NOT use to count fiber providers at a single facility (use get_facility) or for IX interconnection-density scores (use analyze_site). 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_fiber_intel accept? +

get_fiber_intel accepts 4 parameters: market, carrier, route_type, include_sources. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_fiber_intel? +

Register the Mcp Server MCP server in PolicyLayer and add a rule for get_fiber_intel: 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_fiber_intel? +

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

Can I rate-limit get_fiber_intel? +

Yes. Add a rate_limit block to the get_fiber_intel 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_fiber_intel completely? +

Set action: deny in the PolicyLayer policy for get_fiber_intel. 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_fiber_intel? +

get_fiber_intel 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 →