// INTEGRATION

Use Intercept with Zed

Add policy enforcement to Zed in one line.

Config file: Zed settings.json via Settings > Editor > Settings

Zed uses context_servers instead of mcpServers.

// BEFORE

A standard MCP server in your Zed config -- no controls.

settings.json

{
  "context_servers": {
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres", "postgresql://localhost/mydb"],
      "env": {}
    }
  }
}

// WITH INTERCEPT

Wrap the server command with Intercept. Same config structure, policy enforced.

settings.json

{
  "context_servers": {
    "postgres": {
      "command": "npx",
      "args": [
        "-y", "@policylayer/intercept",
        "-c", "policy.yaml",
        "--",
        "npx", "-y", "@modelcontextprotocol/server-postgres",
        "postgresql://localhost/mydb"
      ],
      "env": {}
    }
  }
}

// WHAT YOU GET

Rate limits

Cap tool calls per minute, hour, or day

Access controls

Allow, deny, or conditionally gate any tool

Spend caps

Limit financial operations with daily thresholds

Audit logs

Full trace of every tool call and policy decision

// EXAMPLE POLICY

policy.yaml

version: "1"
default: deny

tools:
  list_customers:
    rules:
      - action: allow
        rate_limit: 30/minute

  create_refund:
    rules:
      - name: "daily cap"
        rate_limit: 10/day

  delete_repository:
    rules:
      - action: deny

// INSTALL

npx -y @policylayer/intercept

github.com/policylayer/intercept →