wavexis_browser_context_close

Close an isolated browser context.

SERVERWavexis SOURCEMathiasPaulenko/wavexis-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/wavexis-mcp/wavexis-browser-context-close.md

WHAT IT DOES

What wavexis_browser_context_close does on Wavexis

AI agents use wavexis_browser_context_close to create or update resources in Wavexis, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wavexis environment.

RISK

Why wavexis_browser_context_close is rated Medium

An AI agent can call wavexis_browser_context_close faster than any human can review: one bad instruction and it creates or modifies resources in Wavexis by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wavexis_browser_context_close safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 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_close, this is the rule to start with:

wavexis_browser_context_close Rate-limited

wavexis_browser_context_close 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wavexis_browser_context_close": {
      "limits": [
        {
          "counter": "wavexis_browser_context_close_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Wavexis, apply this rule, and every wavexis_browser_context_close call is checked against it from then on.

FAQ

Questions about wavexis_browser_context_close

What does the wavexis_browser_context_close tool do? +

Close an isolated browser context. It is categorised as a Write tool in the Wavexis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wavexis_browser_context_close? +

Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_browser_context_close: 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 Wavexis. Nothing to install.

What risk level is wavexis_browser_context_close? +

wavexis_browser_context_close is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wavexis_browser_context_close? +

Yes. Add a rate_limit block to the wavexis_browser_context_close 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.

How do I block wavexis_browser_context_close completely? +

Set action: deny in the PolicyLayer policy for wavexis_browser_context_close. 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.

What MCP server provides wavexis_browser_context_close? +

wavexis_browser_context_close is provided by the 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.

KEEP EXPLORING

More on Wavexis, and thousands of servers like it.

This server

All 195 Wavexis tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →