Query a specific historical trace file (post-hoc analysis). Args: file_path: Path to the .jsonl trace file. mode: Same as trace_property_access (summary/timeline/sequence/search). filter_object: Filter by object name. search_query: Filter by search string. limit: Max events for sequence mode. buc...
AI agents call query_trace_file to retrieve information from Camoufox Reverse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
query_trace_file is a read-only analysis tool that retrieves and filters historical trace data from .jsonl files. While it accesses detailed browser session artifacts (function calls, property access events, network activity), it does not modify, execute, or delete data.
From the tool's definition Tool performs post-hoc analysis of trace files with query operations: 'Query a specific historical trace file', 'filter_object', 'search_query', 'summary/timeline/sequence/search' modes. No modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access query_trace_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Camoufox Reverse, and nothing reaches the server without passing your rules. This is the rule we recommend for query_trace_file:
{
"version": "1",
"default": "deny",
"tools": {
"query_trace_file": {}
}
}query_trace_file 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.
Query a specific historical trace file (post-hoc analysis). Args: file_path: Path to the .jsonl trace file. mode: Same as trace_property_access (summary/timeline/sequence/search). filter_object: Filter by object name. search_query: Filter by search string. limit: Max events for sequence mode. bucket_ms: Bucket size for timeline mode. It is categorised as a Read tool in the Camoufox Reverse MCP Server, which means it retrieves data without modifying state.
Register the Camoufox Reverse MCP server in PolicyLayer and add a rule for query_trace_file: 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 Camoufox Reverse. Nothing to install.
query_trace_file 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 query_trace_file 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 query_trace_file. 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.
query_trace_file is provided by the Camoufox Reverse MCP server (whitenightshadow/camoufox-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Camoufox Reverse tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 Camoufox Reverse tools catalogued and risk-classified — across an index of 42,500+ MCP servers.