electron_debug_status

Check status of dual-CDP debug sessions launched by electron_launch_debug.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/electron-debug-status.md

WHAT IT DOES

What electron_debug_status does on Jshookmcp

AI agents call electron_debug_status to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why electron_debug_status is rated Low

Queries CDP session status without side effects or data manipulation.

From the tool's definition Check status of debug sessions; no modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs electron_debug_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For electron_debug_status, this is the rule to start with:

electron_debug_status Allowed

electron_debug_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "electron_debug_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every electron_debug_status call is checked against it from then on.

FAQ

Questions about electron_debug_status

What does the electron_debug_status tool do? +

Check status of dual-CDP debug sessions launched by electron_launch_debug. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on electron_debug_status? +

Register the Jshook MCP server in PolicyLayer and add a rule for electron_debug_status: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Jshookmcp. Nothing to install.

What risk level is electron_debug_status? +

electron_debug_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit electron_debug_status? +

Yes. Add a rate_limit block to the electron_debug_status rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block electron_debug_status completely? +

Set action: deny in the PolicyLayer policy for electron_debug_status. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides electron_debug_status? +

electron_debug_status is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →