Troubleshoot MCP Registry

After you restart Cursor, confirm the JFrog sessionStart hook is registered and running.

To verify the Agent Guard is active in Cursor:

1. In Cursor, open a new Agent window to trigger the hook.
2. Select Settings > Hooks, and inspect the Execution Log below the hook entry. The most recent run should show input and output.
   • If the hook entry is missing, or the Execution Log shows no recent runs, the plugin did not load. Verify the plugin is installed in Cursor Settings > Plugins, then fully close and reopen Cursor.
   • If the hook ran but the Output is empty, the force-enable flag is not set. Set JF_AGENT_GUARD_FORCE_ENABLE=true, and restart Cursor.

To verify the Agent Guard is active in Claude Code:

1. Select the Installed tab.
2. Confirm the jfrog @ claude-plugins-official plugin is listed with:
   • Status: Enabled
   • Version: 0.1.1 or higher
   • Installed components include:
     • Hooks: SessionStart

VS Code does not expose installed hooks in a user interface. Instead, verify the JFrog plugin sessionStart hook by confirming the file it writes into your workspace.

To verify the Agent Guard is active in VS Code:

1. Fully quit VS Code (Cmd+Q on macOS, or close all windows on Windows), and reopen it.

2. Open a project folder in VS Code (File > Open Folder).

3. Confirm the file exists. In the Explorer panel, open the .github folder and look for copilot-instructions.md. Alternatively, open Quick Open (Cmd/Ctrl+P), and type .github/copilot-instructions.md. The file should open.

   If .github/copilot-instructions.md is missing:

   • Confirm JF_AGENT_GUARD_FORCE_ENABLE=true is set in the environment VS Code inherited.
   • Confirm the JFrog plugin is installed and trusted (Extensions panel, filter @agentPlugins).
   • On Windows, the PowerShell execution policy must allow .ps1 scripts. See Get-ExecutionPolicy.
   • Fully close and reopen VS Code (close all windows, not only reload).

A tool policy or regex pattern might be broader than you intended. Review your regex patterns in Configure Tool Policies. A broad pattern can allow more tools than you meant to permit.

Agent Guard does not install runtimes. Ensure Docker, Python, or Node is installed locally, or confirm the MCP server's required environment variables are set.

MCP permissions are project-specific. Ensure you allowed the MCP for the project configured in your environment, and confirm regex patterns on your tool policies are not blocking the tools.

Make your prompt explicit (accurate and clear) that you want MCPs or tools from the JFrog MCP Registry. Name the server or capability you expect when possible so the agent can match registry entries.

JFrog MCP Registry runs the MCP through AI analysis to predict the tools it exposes. This helps you set up policies before you download the tool, but the list is a discovered suggestion list, not a hard-coded manifest.

Some MCPs require environment variables (such as API keys) to function. Pre-populate them on the Config tab of the MCP details page, or define them locally when you add MCP servers.

Before you add an MCP to your allowed list, open the server card on the Discovery tab. Review the Licenses tab and malicious status so the server meets your organization's compliance standards.

See Allow MCP Servers.

See Configure Tool Policies to create Allow and Deny lists.

Uninstall the JFrog plugin from your IDE's plugin or extension manager. Agent Guard stops automatically when the plugin is removed.

You configure runtime arguments when you add a server to the registry.

To configure runtime arguments for a server:

1. When adding a server to the registry, proceed to Step 2: Configuration in the Add to Registry wizard.
2. Click the Runtime arguments tab (next to the Environment variables tab), and enter your configuration.
3. After saving, you can view the configured runtime arguments at any time on the Configuration tab of the MCP Server Details page.

To set environment variables as secrets:

1. During Step 2 (Configuration) of the Add to Registry wizard, navigate to the Environment variables tab.
2. Next to the environment variable you are configuring, click the Secret toggle to turn it on.