Get detailed variable information from a specific scope when paused at a breakpoint.
AI agents call get_scope_variables to retrieve information from ReverseCraft DevTools MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries variable state from the debugger's call frame without modifying data, executing code, or causing side effects. It is purely informational inspection during an already-paused debugging session. The context of a breakpoint-paused state further confirms this is a passive read operation typical of debugging tools.
From the tool's definition Tool description states it 'Get[s] detailed variable information from a specific scope when paused at a breakpoint.' The verb 'get' and the read-only nature of inspecting variables during debugging indicate no modification or execution of code occurs.
Documented attack patterns abuse exactly the kind of access get_scope_variables gives an agent:
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_scope_variables:
{
"version": "1",
"default": "deny",
"tools": {
"get_scope_variables": {}
}
}get_scope_variables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed variable information from a specific scope when paused at a breakpoint. It is categorised as a Read tool in the ReverseCraft DevTools MCP MCP Server, which means it retrieves data without modifying state.
Register the ReverseCraft DevTools MCP server in PolicyLayer and add a rule for get_scope_variables: 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.
get_scope_variables is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_scope_variables 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.
Set action: deny in the PolicyLayer policy for get_scope_variables. 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.
get_scope_variables 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.
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.
Free to start. No card required.
46 ReverseCraft DevTools MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.