Save a network request and response to a local file in raw HTTP format.
AI agents use save_network_request 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.
The tool writes data (HTTP requests/responses) to disk. While it does not delete or irreversibly modify existing data, and does not execute arbitrary code or move money, it does create or persist data locally. This is a Write operation.
From the tool's definition Tool description explicitly states 'Save a network request and response to a local file' - this creates/writes data to the filesystem in raw HTTP format.
Documented attack patterns abuse exactly the kind of access save_network_request 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_network_request:
{
"version": "1",
"default": "deny",
"tools": {
"save_network_request": {
"limits": [
{
"counter": "save_network_request_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_network_request 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 a network request and response to a local file in raw HTTP format. 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_network_request: 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_network_request 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_network_request 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_network_request. 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_network_request 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.