Take a screenshot of the current Camoufox browser page.
AI agents call mcp_browser_use__camoufox_screenshot to retrieve information from MCP Browser Use without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshots capture visual data from a webpage without modifying, executing code, deleting, or transferring funds. This is a pure observation action typical of Read operations. Severity is low because screenshots do not modify system state or expose sensitive data differently than normal browsing; an AI agent taking screenshots poses minimal direct risk.
From the tool's definition Tool name 'screenshot' and description 'Take a screenshot of the current Camoufox browser page' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access mcp_browser_use__camoufox_screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Browser Use, and nothing reaches the server without passing your rules. This is the rule we recommend for mcp_browser_use__camoufox_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"mcp_browser_use__camoufox_screenshot": {}
}
} mcp_browser_use__camoufox_screenshot 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.
Take a screenshot of the current Camoufox browser page. It is categorised as a Read tool in the MCP Browser Use MCP Server, which means it retrieves data without modifying state.
Register the MCP Browser Use MCP server in PolicyLayer and add a rule for mcp_browser_use__camoufox_screenshot: 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 MCP Browser Use. Nothing to install.
mcp_browser_use__camoufox_screenshot 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 mcp_browser_use__camoufox_screenshot 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 mcp_browser_use__camoufox_screenshot. 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.
mcp_browser_use__camoufox_screenshot is provided by the MCP Browser Use MCP server (janspoerer/mcp_browser_use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Browser Use, 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.
9 MCP Browser Use tools catalogued and risk-classified — across an index of 43,000+ MCP servers.