Save all scope variables from the current debug context to a JSON file.
AI agents use save_scope_variables to create or update resources in ReverseCraft DevTools MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ReverseCraft DevTools MCP environment.
This tool writes debugging context data (scope variables) to a file system artifact in JSON format. While it does not delete or irreversibly modify existing data, it does persist new data to disk. The scope variables may contain sensitive information (credentials, tokens, user data from the current debug session), making unauthorized writes a medium severity concern.
From the tool's definition Tool name and description indicate it 'Save[s]' scope variables 'to a JSON file', which creates/writes data to storage.
Documented attack patterns abuse exactly the kind of access save_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 save_scope_variables:
{
"version": "1",
"default": "deny",
"tools": {
"save_scope_variables": {
"limits": [
{
"counter": "save_scope_variables_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_scope_variables stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Save all scope variables from the current debug context to a JSON file. It is categorised as a Write tool in the ReverseCraft DevTools MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ReverseCraft DevTools MCP server in PolicyLayer and add a rule for save_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.
save_scope_variables is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_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 save_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.
save_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.