plan_fiber_leadin
Plan N diverse, road-following fibre lead-in routes from a candidate data-center site to a carrier hotel / POP, with indicative build cost and a route-diversity read. Answers "can I get N diverse fibre routes into this site, how far, how much, and where do they share a corridor?". Example: plan_f...
This record as markdown: /tools/cloud-dchub-mcp-server/plan-fiber-leadin.md
What plan_fiber_leadin does on Mcp Server
AI agents call plan_fiber_leadin 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 |
|---|---|---|---|
n | integer | — | Number of diverse routes to plan, 1-6 (default 4) |
to | string | — | Destination carrier hotel/POP as "lat,lng" OR an address, e.g. "20 Wharf Street, Brisbane City QLD" |
from | string | — | Origin site as "lat,lng" OR a street address, e.g. "250 Paringa Road, Murarrie QLD" |
fibre | string | — | Fibre count spec for cost estimate: "720F" or "1440F" |
bore_m | integer | — | River/rail bore length in metres to add to the route, 0-100000 (optional) |
Parameters from the server's own tool schema.
Why plan_fiber_leadin is rated Low
The tool performs route planning and cost estimation analysis — it retrieves and computes data about potential fibre routes without creating, modifying, or executing anything in an external system. It returns informational output (distances, costs, diversity analysis) based on input parameters. No data is written, deleted, or financially committed.
From the tool's definition Plan N diverse, road-following fibre lead-in routes... with indicative build cost and a route-diversity read. Answers 'can I get N diverse fibre routes into this site, how far, how much, and where do they share a corridor?'
Attacks that exploit this kind of access
The rule that runs plan_fiber_leadin 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 plan_fiber_leadin, this is the rule to start with:
plan_fiber_leadin 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 plan_fiber_leadin call is checked against it from then on.
Questions about plan_fiber_leadin
Plan N diverse, road-following fibre lead-in routes from a candidate data-center site to a carrier hotel / POP, with indicative build cost and a route-diversity read. Answers "can I get N diverse fibre routes into this site, how far, how much, and where do they share a corridor?". Example: plan_fiber_leadin from="250 Paringa Road, Murarrie QLD" to="20 Wharf Street, Brisbane City QLD" n=4. Params: from (lat,lng OR street address), to (lat,lng OR address — e.g. a NextDC/Equinix POP), n (1-6 routes, default 4), fibre ("720F"|"1440F"), bore_m (river/rail bore length in metres, optional). Returns per-route length_km + GeoJSON geometry, total_route_km, diversity {min_separation_m_midhaul, shared_street_km}, and indicative cost {capex_usd, opex_usd_yr}. INDICATIVE auto-routed road corridors — NOT engineered alignments; subject to survey, DBYD and carrier confirmation. Do NOT use for a single site-suitability score (use analyze_site) or fibre-provider footprints (use get_fiber_intel). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
plan_fiber_leadin accepts 5 parameters: n, to, from, fibre, bore_m. 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 plan_fiber_leadin: 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.
plan_fiber_leadin 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 plan_fiber_leadin 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 plan_fiber_leadin. 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.
plan_fiber_leadin 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