DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to require approval for risky Cursor shell and MCP calls with Jev Guard

Install the Cursor guard so shell and MCP tool calls are denied or sent for approval.

Who it is forA Cursor user who lets the agent run shell commands and MCP tools and wants a check before risky ones execute.

The problemCursor agents can run shell and MCP calls that touch files or external services, and a single bad call can cause real damage.

The outcomeDestructive shell and MCP calls are denied, risky ones ask for approval, and tool results are scanned for injected instructions.

What you need first

  • Node.js and npm, to install the jev-guard package or run the install commands
  • One provider key: a TypeSafe key from console.typesafe.ai, a vck_ Vercel AI Gateway key, or an sk-or- OpenRouter key
  • The coding agent you want to guard, installed on the same machine

Steps

  1. Run npm i -g jev-guard
  2. Run jev-guard key "…" with your provider key
  3. Run jev-guard install cursor
  4. Restart Cursor and trigger a shell call to confirm the approval prompt appears

Prompt for your agent

Install jev-guard for Cursor on this machine with `jev-guard install cursor` and report the path of the hooks file it wrote. Do not run any shell command that changes files.

Caveat. The README says Cursor's preToolUse cannot ask, so the ask decision applies only to shell and MCP calls, not every tool.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page