Get accessibility tree snapshot — the PRIMARY way to read page content. Returns element refs, roles, names and values. Token-efficient. Always prefer over screenshot. Refs come from the accessibility tree, so custom SPA elements may be missing; fall back to CSS selectors, camofox_wait_for_selecto...
AI agents call snapshot to retrieve information from Camofox without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
While this is a Read operation (retrieves page content), it carries medium severity because: (1) it operates within an anti-detection browser automation context that could be misused for unauthorized data scraping, credential theft, or privacy violations; (2) the accessibility tree can expose sensitive page content and structure; (3) when combined with sibling Execute tools (batch_click, camofox_evaluate_js) it…
From the tool's definition Tool description states 'Get accessibility tree snapshot — the PRIMARY way to read page content' and 'Returns element refs, roles, names and values.' This is fundamentally a retrieval operation that queries page state without modification.
Documented attack patterns abuse exactly the kind of access snapshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Camofox, and nothing reaches the server without passing your rules. This is the rule we recommend for snapshot:
{
"version": "1",
"default": "deny",
"tools": {
"snapshot": {}
}
}snapshot 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.
Get accessibility tree snapshot — the PRIMARY way to read page content. Returns element refs, roles, names and values. Token-efficient. Always prefer over screenshot. Refs come from the accessibility tree, so custom SPA elements may be missing; fall back to CSS selectors, camofox_wait_for_selector, or camofox_get_page_html when needed. It is categorised as a Read tool in the Camofox MCP Server, which means it retrieves data without modifying state.
Register the Camofox MCP server in PolicyLayer and add a rule for snapshot: 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 Camofox. Nothing to install.
snapshot 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 snapshot 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 snapshot. 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.
snapshot is provided by the Camofox MCP server (redf0x1/camofox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 Camofox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 Camofox tools catalogued and risk-classified — across an index of 42,500+ MCP servers.