AI agents use set_user_agent to create or update resources in JS Reverse Strong MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JS Reverse Strong MCP environment.
This tool modifies browser state (user-agent header) in a reversible manner. It does not execute arbitrary code, delete data, move money, or trigger irreversible actions. The modification is limited to HTTP headers sent by the browser and can be undone by resetting to default or setting a different value.
From the tool's definition Tool name 'set_user_agent' and description 'Set custom user-agent for active page' indicates modification of request headers for the active browser session.
Documented attack patterns abuse exactly the kind of access set_user_agent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JS Reverse Strong MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for set_user_agent:
{
"version": "1",
"default": "deny",
"tools": {
"set_user_agent": {
"limits": [
{
"counter": "set_user_agent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_user_agent stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set custom user-agent for active page. It is categorised as a Write tool in the JS Reverse Strong MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the JS Reverse Strong MCP server in PolicyLayer and add a rule for set_user_agent: 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 JS Reverse Strong MCP. Nothing to install.
set_user_agent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_user_agent 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 set_user_agent. 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.
set_user_agent is provided by the JS Reverse Strong MCP server (lwjjike/jsreverser-strong-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JS Reverse Strong MCP, 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.
85 JS Reverse Strong MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.