Skip to main content
Book a demo

Connect Datadog to VS Code

Give VS Code governed access to Datadog’s 414 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo VS Code setup guide

Set up

Add Datadog to VS Code in four steps

Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.

  1. 1

    Approve Datadog in Runlayer

    Add Datadog from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Datadog’s 414 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 3

    Sign in to Datadog

    Each user signs in to Datadog with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Datadog from VS Code

    Datadog’s approved tools appear in VS Code. Every call is checked against policy and recorded.

Tools

414 Datadog tools in VS Code

Runlayer policy decides which of these VS Code users can call.

  • Dd gff

    Do-not-call

  • Dd guc

    Do-not-call

  • Dd rfw

    Do-not-call

  • Dd wfd

    Do-not-call

  • Aap get activation options

    Aap get activation options.

  • Aap onboarding

    Returns the authoritative step-by-step instructions for enabling Datadog App and API Protection (AAP) to monitor and secure your application.

  • Add comment to Datadog case

    Add a comment to a Datadog Work Item (also called a Case) timeline.

  • Add llmobs annotation queue interactions

    Queue traces, sessions, or spans for human review in an annotation queue.

See all 414 Datadog tools

Control

What Runlayer can see and stop in VS Code

Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.

  • Gateway policy (available)

    Every Datadog call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, VS Code as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination