Skip to content

VS Code Power Strip Security check_prompt_injection

How to: VS Code Power Strip Security check_prompt_injection

client:VS Code transport:streamable-http tool:check_prompt_injection

Add Power Strip Security to VS Code

  1. 01

    Open .vscode/mcp.json and merge this in. Keep any servers already there.

{
  "servers": {
    "power-strip-security": {
      "type": "http",
      "url": "https://api.powerstripsecurity.workers.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

    Ask for something check_prompt_injection does. VS Code lists the server's tools on connect and calls check_prompt_injection itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Power Strip Security's identifier in your config matches the one above exactly.

Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs

Set these first

Power Strip Security will not start until these are set, so check_prompt_injection never becomes available.

  • PSS_PRIVATE_KEY
  • PSS_MAX_SPEND_USD

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.