MCP control

MCP tool allowlists for IDE coding agents. Decide which MCP tools and actions agents may call. Draft a PR—yes. Hit prod APIs or secret stores—not without an approval path.

Why it matters

MCP expands what an IDE agent can reach. Without org-wide allowlists, each laptop’s MCP config becomes an ungoverned integration surface.

Allow and deny examples

Allow

• github.read, pr.draft, catalog lookup

Deny

• secrets.read, kube.apply, unrestricted HTTP

How it works

When an agent selects an MCP tool, Relay evaluates MCP scopes before the tool runs. Approved calls proceed; denied calls return a structured reason and are recorded for audit.

For platform MCP used by DevX Assist Copilot and Harness gateway tools, see Tools & MCP, Copilot for DevX Assist, and Gateway—Relay MCP control is specifically the IDE coding-agent channel.