AI agents call get_request_initiator 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.
The tool name and server context indicate this retrieves information about what initiated a network request (stack trace, source, etc.)—a read-only observation operation typical of debugging tools. No mutations, code execution, or external side effects are implied. Low severity due to information disclosure scope limited to request metadata.
From the tool's definition Tool name 'get_request_initiator' suggests retrieval of request metadata; description is empty but context from sibling tools (analyze_cookie_sources, get_console_logs, get_network_request) indicates this is a browser inspection/observation tool with no…
Documented attack patterns abuse exactly the kind of access get_request_initiator 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 get_request_initiator:
{
"version": "1",
"default": "deny",
"tools": {
"get_request_initiator": {}
}
} get_request_initiator 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_request_initiator. 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 get_request_initiator: 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.
get_request_initiator 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 get_request_initiator 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 get_request_initiator. 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.
get_request_initiator 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.