Removes a previously installed function hook.
AI agents invoke unhook_function to trigger actions in JS Reverse Strong MCP. 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.
Unhooking a function alters the runtime execution environment by restoring or removing instrumentation previously injected. This is an Execute-level operation because it triggers a change in how code runs (removing hooks affects control flow and observability), though it does not irreversibly destroy data. Misuse could silently disable security monitoring or anti-tamper hooks, hence medium severity.
From the tool's definition 'Removes a previously installed function hook' — modifies the runtime state of a hooked function in a live browser/JS environment
Documented attack patterns abuse exactly the kind of access unhook_function 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 unhook_function:
{
"version": "1",
"default": "deny",
"tools": {
"unhook_function": {
"limits": [
{
"counter": "unhook_function_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}unhook_function 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.
Removes a previously installed function hook. It is categorised as a Execute tool in the JS Reverse Strong MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the JS Reverse Strong MCP server in PolicyLayer and add a rule for unhook_function: 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.
unhook_function 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 unhook_function 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 unhook_function. 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.
unhook_function 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.