Create a new browser session with intelligent auto-close and session management
AI agents invoke create_browser_session to trigger actions in ZMCPTools. 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 browser session initiates an external browser process/resource whose effects depend on subsequent actions. It's an operational trigger that establishes a live browser environment, not merely reading data or writing a record. This falls under Execute as it launches an external operation (browser automation session) whose scope and impact depend on how it's used.
From the tool's definition Create a new browser session with intelligent auto-close and session management
Documented attack patterns abuse exactly the kind of access create_browser_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for create_browser_session:
{
"version": "1",
"default": "deny",
"tools": {
"create_browser_session": {
"limits": [
{
"counter": "create_browser_session_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}create_browser_session 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.
Create a new browser session with intelligent auto-close and session management. It is categorised as a Execute tool in the ZMCPTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for create_browser_session: 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 ZMCPTools. Nothing to install.
create_browser_session 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 create_browser_session 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 create_browser_session. 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.
create_browser_session is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.