wavexis_browser_context_create
Create an isolated browser context within a session.
This record as markdown: /tools/wavexis-mcp/wavexis-browser-context-create.md
What wavexis_browser_context_create does on Pypi:wavexis
AI agents invoke wavexis_browser_context_create to trigger actions in Pypi:wavexis. 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.
Why wavexis_browser_context_create is rated High
Creating a browser context initiates a new browsing environment (similar to a new browser profile/incognito session) within an active session. This is an Execute-level action as it triggers external browser operations and establishes an environment in which further browser automation can occur.
From the tool's definition Create an isolated browser context within a session
Attacks that exploit this kind of access
The rule that runs wavexis_browser_context_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pypi:wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_browser_context_create, this is the rule to start with:
wavexis_browser_context_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Pypi:wavexis, apply this rule, and every wavexis_browser_context_create call is checked against it from then on.
Questions about wavexis_browser_context_create
Create an isolated browser context within a session. It is categorised as a Execute tool in the Pypi:wavexis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pypi:wavexis MCP server in PolicyLayer and add a rule for wavexis_browser_context_create: 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 Pypi:wavexis. Nothing to install.
wavexis_browser_context_create 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 wavexis_browser_context_create 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 wavexis_browser_context_create. 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.
wavexis_browser_context_create is provided by the Pypi:wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pypi:wavexis, and thousands of servers like it.
Across the catalogue