Select a page as a context for future tool calls.
AI agents call select_page 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 selects/sets an active page context for subsequent operations. It doesn't read, write, execute, or delete data — it simply changes which page is targeted for future tool calls. This is a navigation/context-setting operation with minimal blast radius on its own.
From the tool's definition Select a page as a context for future tool calls
Documented attack patterns abuse exactly the kind of access select_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 select_page:
{
"version": "1",
"default": "deny",
"tools": {
"select_page": {}
}
} select_page 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.
Select a page as a context for future tool calls. 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 select_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.
select_page 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 select_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 select_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.
select_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.