get_debugger_status

THE RISK

Low Risk

Why get_debugger_status needs a policy

This tool purely queries and retrieves information about the current state of the JavaScript debugger. It has no side effects—it does not modify code, execute scripts, delete data, or trigger external operations. It falls squarely into the Read category.

From the tool's definition Tool name 'get_debugger_status' and description 'Get the current status' indicate a retrieval operation. The description specifies reading debugger state: 'call stack, code context, and scope variables' with no modification, deletion, or execution of external…

Documented attack patterns abuse exactly the kind of access get_debugger_status gives an agent:

POLICY

How to control get_debugger_status

PolicyLayer is an MCP gateway — it sits between your AI agents and ReverseCraft DevTools MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_debugger_status:

policy.json

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

get_debugger_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register ReverseCraft DevTools MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More ReverseCraft DevTools MCP tools

Destructive clear_cookies Clear browser cookies for all sites or a specific domain. Destructive clear_persistent_scripts Remove all registered persistent scripts for the current page at once. This is useful for Destructive clear_script_replacements Remove all script replacement rules for the current page. Destructive remove_persistent_script Remove a previously registered persistent script by its identifier. After removal, the sc Destructive remove_script_replacement Remove a script replacement rule by its ID. Destructive remove_xhr_breakpoint Remove a previously set XHR/Fetch breakpoint by its URL pattern, or remove all XHR breakpo Destructive close_page Closes the page by its index. The last open page cannot be closed. Execute navigate_page Navigates the currently selected page to a URL.

All 46 ReverseCraft DevTools MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_debugger_status

What does the get_debugger_status tool do? +

Get the current status of the JavaScript debugger including call stack, code context, and scope variables. It is categorised as a Read tool in the ReverseCraft DevTools MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_debugger_status? +

Register the ReverseCraft DevTools MCP server in PolicyLayer and add a rule for get_debugger_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 ReverseCraft DevTools MCP. Nothing to install.

What risk level is get_debugger_status? +

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

Can I rate-limit get_debugger_status? +

Yes. Add a rate_limit block to the get_debugger_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 get_debugger_status completely? +

Set action: deny in the PolicyLayer policy for get_debugger_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 get_debugger_status? +

get_debugger_status is provided by the ReverseCraft DevTools MCP server (reverse-craft/rc-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ReverseCraft DevTools MCP tool call.

Start from ReverseCraft DevTools MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →