tool_browser_screenshot
AI agents call tool_browser_screenshot to retrieve information from Frappe MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Taking a screenshot is a read-only operation that captures visual information about the current state of a browser window without creating, modifying, deleting, or executing any code. The blast radius is minimal—misuse would only expose what is currently visible on screen. Confidence is 0.85 rather than higher because the description is empty, preventing confirmation of any side effects or special behavior.
From the tool's definition Tool name 'tool_browser_screenshot' indicates a screenshot capture action. Given the sibling tools include browser control operations (tool_browser_close, tool_browser_press_key, tool_browser_type) and the server manages Frappe benches, this tool retrieves…
Attacks that exploit this kind of access
tool_browser_screenshot. It is categorised as a Read tool in the Frappe MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Frappe MCP Server MCP server in PolicyLayer and add a rule for tool_browser_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 Frappe MCP Server. Nothing to install.
tool_browser_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 tool_browser_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 tool_browser_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.
tool_browser_screenshot is provided by the Frappe MCP Server MCP server (kallusuvaidyam/frappe_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →