Enable outgoing TLS + HTTP/2 fingerprint spoofing via impit (native TLS impersonation, no Docker required). Supports browser presets that select an impit target (rustls, matching real Chrome/Firefox).
AI agents invoke proxy_set_fingerprint_spoof to trigger actions in Proxy. 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.
This tool triggers an external operation that modifies how outgoing TLS handshakes are presented to remote servers, effectively impersonating browser TLS/HTTP2 fingerprints. This is not a simple configuration write — it enables active deception of remote endpoints, which can be used to bypass bot detection, evade security controls, or facilitate man-in-the-middle attacks.
From the tool's definition 'Enable outgoing TLS + HTTP/2 fingerprint spoofing via impit (native TLS impersonation)' — actively configures TLS fingerprint impersonation to make traffic appear as a different client (Chrome/Firefox)
Documented attack patterns abuse exactly the kind of access proxy_set_fingerprint_spoof gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for proxy_set_fingerprint_spoof:
{
"version": "1",
"default": "deny",
"tools": {
"proxy_set_fingerprint_spoof": {
"limits": [
{
"counter": "proxy_set_fingerprint_spoof_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}proxy_set_fingerprint_spoof 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.
Enable outgoing TLS + HTTP/2 fingerprint spoofing via impit (native TLS impersonation, no Docker required). Supports browser presets that select an impit target (rustls, matching real Chrome/Firefox). It is categorised as a Execute tool in the Proxy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Proxy MCP server in PolicyLayer and add a rule for proxy_set_fingerprint_spoof: 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 Proxy. Nothing to install.
proxy_set_fingerprint_spoof 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 proxy_set_fingerprint_spoof 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 proxy_set_fingerprint_spoof. 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.
proxy_set_fingerprint_spoof is provided by the Proxy MCP server (yfe404/proxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Proxy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
89 Proxy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.