MCP Tool Reference High Risk

close_page

Close a browser page

Part of the Chrome DevTools MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

WHEN AI AGENTS USE THIS TOOL

AI agents invoke close_page to trigger processes or run actions in Chrome DevTools. Execute operations can have side effects beyond the immediate call — triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

WHY ENFORCE A POLICY ON CLOSE_PAGE

close_page can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

chrome-devtools.yaml
tools:
  close_page:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Chrome DevTools policy for all 29 tools.

DETAILS

Tool Name

close_page

Category

Execute

Risk Level

High

MORE CHROME DEVTOOLS TOOLS

View all 29 tools →

SIMILAR EXECUTE TOOLS ON OTHER SERVERS

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the close_page tool do?

Close a browser page. It is categorised as a Execute tool in the Chrome DevTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on close_page?

Add a rule in your Intercept YAML policy under the tools section for close_page. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Chrome DevTools MCP server.

What risk level is close_page?

close_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit close_page?

Yes. Add a rate_limit block to the close_page rule in your Intercept 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 close_page completely?

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

What MCP server provides close_page?

close_page is provided by the Chrome DevTools MCP server (ChromeDevTools/chrome-devtools-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

ENFORCE POLICIES ON CHROME DEVTOOLS

Open source. One binary. Zero dependencies.