Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.equinix.dev/llms.txt

Use this file to discover all available pages before exploring further.

The promise: the failure mode of a poorly-prompted agent is a closed PR, not a misconfigured Cloud Router. Every guarantee on this page is enforced at the package level — not relied on at the prompt level.

​
Six safety controls

Plan-only by default

Every Terraform output ships with prevent_destroy and an apply guard. The default execution mode is dry-run. Control: F-001

Scoped MCP identities

Agents authenticate as network-agent-mcp@ users with project, metro, and resource scopes. Personal admin identities are never used for OAuth consent. Control: F-014

Account-aware preflight

Five blocking gates run before any mutating tool: ports/devices, observability permission, developer app, capacity confirmation, provider quote. Control: F-022

pricing.md governance

The agent reads commercial estimates from a versioned pricing.md contract. Anything missing is reported as quote_required rather than fabricated. Control: F-031

Audit log per plan

Every plan run captures the prompt, the read tools, the blocked mutating tools, the timestamp, and the dedicated MCP user. Logs export as JSON or to a customer SIEM webhook. Control: F-040

Reviewer-grade Terraform

Output is shaped to be reviewable in a PR — modules, lifecycle blocks, apply guards, and explicit quote-status fields the reviewer can grep for before merging. Control: F-052

​
What an agent literally cannot do

Generated HCL ships with lifecycle { prevent_destroy = true } on every resource. The CLI never invokes terraform apply — only terraform init -backend=false and terraform validate.To actually apply, a human reviewer opens the generated PR, edits out the apply guard, and runs terraform apply against their own backend.
Mutating MCP tools are gated by the confirmation envelope:
{
  "tool": "equinix_fabric_create_router",
  "mode": "mutating",
  "requires_confirmation": true,
  "blocked_by": [
    "official_quote_missing",
    "developer_app_missing",
    "account_assets_missing"
  ]
}
The agent receives this envelope instead of a tool result, with no execution side-effect.
pricing.md records carry an agent_instruction field. Common values:
  • use_for_directional_estimate_only — fine to quote
  • require_account_team_confirmation_before_apply — gate
  • quote_required — fabricating a number is a violation
Anything outside use_for_directional_estimate_only falls back to quote.
The MCP profile expects a dedicated user identity (network-agent-mcp@company.com) scoped to the project. Personal admin OAuth is rejected at the MCP layer.
Every plan run writes a JSONL line to .equinix-dev/audit/<run-id>.jsonl with the prompt, the read tools, the blocked mutating tools, the timestamp, and the agent identity. The CLI cannot write to a real Equinix account without first appending an entry; the local explorer can stream the same shape to a customer SIEM webhook.

​
What still requires a human

The cleanest mental model: an agent can compile, validate, price, and document everything. A human signs the PR and types terraform apply. There is no autonomous mode.
1

Resolve preflight blockers

The five readiness gates — local manifest, money guard, Terraform mapping, developer app, account assets — must all pass before any mutating call is even attempted. Two of those (developer app, account assets) are administrative actions on the Equinix portal that only a human can complete.
2

Approve the Terraform PR

The PR review is a real PR review. The reviewer’s job is to read the HCL, check the pricing patch, validate the module versions, and either approve or request changes.
3

Run terraform apply

The reviewer or platform engineer runs terraform apply against their own backend, with their own credentials. equinix.dev never holds those credentials.
4

Confirm mutating MCP tools

For surfaces that aren’t Terraform-shaped (e.g., creating a streaming subscription via MCP), the MCP client prompts the user to confirm each call. The CLI shows the confirmation envelope and the human types y/n.

​
Compliance roadmap

This is a concept-grade roadmap. Real compliance scope is set by Equinix’s existing programs.
ItemStatus
SOC 2 Type IIIn audit · Q3 2026
ISO 27001Scoped · 2027
HIPAABAA on request
FedRAMPVia Equinix Government Cloud
Subprocessors (local demo)None