Skip to content
PERMISSION/PROTOCOL
← Integrations

MCP Guard setup path

Put policy on the MCP server path you control.

MCP Guard evaluates tools/call requests passing between a client and its configured stdio server. Start with one server and a small set of tool rules.

Review MCP Guard setup Walk through an approval

What setup requires.

  1. 01

    Choose a stdio MCP server and confirm how the client launches it.

  2. 02

    Run the server through MCP Guard and review decisions in observe mode.

  3. 03

    Switch to enforcement and confirm a held call returns an error instead of reaching the server.

  4. 04

    Test allowed, blocked, and held calls using the installed version.

Coverage and limits.

  • Observe mode forwards calls without blocking.
  • Without the optional approval UI, a require-approval rule returns a hold error. The approval UI in 0.1.0 has no sign-in, so use it only to evaluate test tools.
  • Local decision records and independently signed authority receipts are different evidence formats. Confirm what your workflow needs.

Have a different execution path?

Bring the action, target system, and required evidence. We can assess the integration work before you commit to a rollout.

Discuss your workflow