Setup in under 5 minutes • Free & Open Source

Try our guardrails in your own repository

See how MandateOS can block your agent’s shady requests in your own repository. A quick 5-minute setup is enough to configure your repository hooks and try out a blocking request.

Hosts
01

Open Cursor on the repository you want to guard

?

You need Node.js with npm available because the installer runs from the published npm package. Cursor Desktop is the tested enforcement surface for these hooks.

Open the repository in Cursor so the terminal starts at the repository root.

Press Ctrl+J on Windows/Linux or Cmd+J on macOS to open the integrated terminal.

02

Add your MandateOS connection values

?

These are public demo credentials with access only to the rate-limited installation demo route (30 evaluations per minute). The guide fetches them from the API rather than bundling them in the website. The installer writes them into Cursor's MCP and hook config; replace them with your own control-panel values when you are ready for a real workspace.

This installation guide provides ready-to-use demo URL, credential, and mandates. They will allow you to test against our demo mandates, but will be replaced with your real credentials later.

We are getting the connection values for you, hang on!

03

Run the Cursor installer

?

The installer updates ~/.cursor/mcp.json, .cursor/mcp.json, and .cursor/hooks.json. The hooks use beforeShellExecution and beforeMCPExecution and fail open if MandateOS is unreachable, so routine host work is not hard-blocked by a bridge failure.

This installs the MandateOS MCP server and Cursor hooks for the current repository. The default setup includes the bundled starter risk presets.

powershell
npx --yes --package @mandate-os/mcp@latest mandate-os-cursor-install install --workspace "$PWD"
04

Approve MandateOS in Cursor

?

The approval is stored by Cursor for this project. If status shows approval files as missing before first launch, that is normal.

If Cursor asks whether to allow the mandateos MCP server, approve it so the agent can reach MandateOS.

text
Use the mandateos_get_context tool and tell me which MandateOS tools are available in this workspace.
05

Verify a guarded action

?

The commands below are wired into the demo mandate so you can see MandateOS stop the agent.

Ask Cursor to run the approval and blocked commands below. In both cases your AI will be blocked from taking action; in practice you can adjust the requirement yourself in the MandateOS dashboard (not available in this demo).

We are getting the connection values for you, hang on!