AI agents invoke new_page to trigger actions in ReverseCraft DevTools MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Creating a new page is an Execute action because it initiates a browser operation whose side effects depend on context and subsequent agent actions. While not inherently destructive, it triggers external processes (browser page instantiation) and could be used in conjunction with other tools (click, evaluate_on_call_frame) to perform unintended automation.
From the tool's definition Tool name 'new_page' with description 'Creates a new page' in the context of a browser automation server (ReverseCraft DevTools MCP).
Documented attack patterns abuse exactly the kind of access new_page 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 new_page:
{
"version": "1",
"default": "deny",
"tools": {
"new_page": {
"limits": [
{
"counter": "new_page_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} new_page stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Creates a new page. It is categorised as a Execute tool in the ReverseCraft DevTools MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ReverseCraft DevTools MCP server in PolicyLayer and add a rule for new_page: 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.
new_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the new_page 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 new_page. 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.
new_page 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.