Skip to main content
Book a demo

Connect Planhat to VS Code

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

Book a demo VS Code setup guide

Set up

Add Planhat 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

    Add Planhat to Runlayer

    Planhat isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  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, Planhat’s 10 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 Planhat

    Sign in the way Planhat requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Planhat from VS Code

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

Tools

10 Planhat tools in VS Code

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

  • Create document

    Create a new document (page) in Planhat.

  • Create model record

    MODEL: "Company", PARAMETERS: {"name": "Acme Corp", "domain": "acme.com"}

  • Delete model record

    Delete existing record.

  • Get document

    Retrieve a document (page) by its ID, including its full content.

  • Get model action parameters

    Returns field metadata (names, types, required flags) for a data model.

  • Get model record

    Get single record by ID.

  • List model records

    MODEL: "Company", LIMIT: 20

  • Search documents

    Search documents (pages) by text.

See all 10 Planhat 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 Planhat 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