inject_stealth · JS Reverse MCP: Risk & Policy

WHAT IT DOES

What inject_stealth does on JS Reverse MCP

AI agents invoke inject_stealth to trigger actions in JS Reverse 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.

WHY IT NEEDS A POLICY

Why inject_stealth needs a policy

This tool executes scripts in the browser context specifically designed to evade detection mechanisms. Injecting stealth scripts is an Execute-category action that runs code in an active browser session. The anti-detection nature significantly raises the severity, as misuse could facilitate malicious automation, fingerprint evasion, or bypass of security controls on target pages.

From the tool's definition Inject anti-detection stealth scripts to current page

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

inject_stealth Rate-limited

inject_stealth 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "inject_stealth": {
      "limits": [
        {
          "counter": "inject_stealth_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches JS Reverse MCP, so you can run agents against it safely.

FAQ

Questions about inject_stealth

What does the inject_stealth tool do? +

Inject anti-detection stealth scripts to current page. It is categorised as a Execute tool in the JS Reverse MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on inject_stealth? +

Register the JS Reverse MCP server in PolicyLayer and add a rule for inject_stealth: 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 MCP. Nothing to install.

What risk level is inject_stealth? +

inject_stealth is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit inject_stealth? +

Yes. Add a rate_limit block to the inject_stealth 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.

How do I block inject_stealth completely? +

Set action: deny in the PolicyLayer policy for inject_stealth. 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.

What MCP server provides inject_stealth? +

inject_stealth is provided by the JS Reverse MCP server (noone-hub/jsreverser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.