Docs

Cursor

The AI editor. Fully covered: commands, file reads, MCP calls and prompts are checked before they run.

What ZYBE can do

Block and Ask, on every rule. Cursor checks with ZYBE before it runs a shell command, reads a file, calls an MCP server, or submits a prompt, and reads ZYBE's answer.

What you do

Install the sensor. Restart Cursor if it was open.

Check it's working

1. In Cursor's AI chat, ask it to run a command.
2. In the console, open the laptop from Inventory, Endpoints, click Sensor. Cursor shows Blocking.

What the developer sees when blocked

Cursor shows ZYBE's reason in the chat and the AI explains it was refused. With Ask, Cursor pauses with the reason and a choice.

MCP servers in Cursor

Cursor's MCP servers are listed in the Inventory under the laptop. Blocking one in the console blocks it in Cursor on every laptop.

Extensions

Cursor runs VS Code extensions. The ones that are AI tools in their own right, Cline and Roo Code, show up as their own agents. See Editor extensions that are agents.

For IT

ZYBE's connection is in ~/.cursor/hooks.json, merged in next to anything else there. On Windows, Cursor runs it through a small .cmd launcher, so Git for Windows must be present.