Offline verify a signing function against user-provided samples. Typical workflow: 1. Capture real signed requests via network_capture + list_network_requests 2. Extract samples into a list 3. Write candidate signing code 4. Call this tool -> get pass_rate + first_divergence 5. Iterate Args: sign...
AI agents invoke verify_signer_offline to trigger actions in Camoufox Reverse. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool accepts and executes arbitrary JavaScript code in the current page context to test a signing function. While framed as an offline verification step, it runs user-supplied JS in a live browser environment, which constitutes code execution.
From the tool's definition 'signer_code: JS evaluating to a function' and 'Runs in current page context' — executes arbitrary JavaScript code supplied by the caller within a live browser page context
Documented attack patterns abuse exactly the kind of access verify_signer_offline 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 verify_signer_offline:
{
"version": "1",
"default": "deny",
"tools": {
"verify_signer_offline": {
"limits": [
{
"counter": "verify_signer_offline_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}verify_signer_offline stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Offline verify a signing function against user-provided samples. Typical workflow: 1. Capture real signed requests via network_capture + list_network_requests 2. Extract samples into a list 3. Write candidate signing code 4. Call this tool -> get pass_rate + first_divergence 5. Iterate Args: signer_code: JS evaluating to a function: (sample) => {param: computed_value}. Runs in current page context. samples: List of sample dicts, each with: - id: user-defined identifier - input: dict passed to signer function - expected: dict of {param_name: expected_value_str} compare_params: Which params to compare. If None, compare all keys in each sample's expected. Returns: dict with total_samples, passed, failed, pass_rate, first_divergence, details. It is categorised as a Execute tool in the Camoufox Reverse MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Camoufox Reverse MCP server in PolicyLayer and add a rule for verify_signer_offline: 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.
verify_signer_offline is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the verify_signer_offline 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 verify_signer_offline. 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.
verify_signer_offline 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.