record_reverse_evidence · JS Reverse MCP: Risk & Policy

WHAT IT DOES

What record_reverse_evidence does on JS Reverse MCP

AI agents use record_reverse_evidence to create or update resources in JS Reverse MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JS Reverse MCP environment.

WHY IT NEEDS A POLICY

Why record_reverse_evidence needs a policy

The tool writes/appends data to a log file (task artifact log). It is a Write operation since it creates or modifies a log record. It does not execute code, delete data, or involve financial transactions. Severity is low as it only appends evidence records to a local artifact log, with limited blast radius if misused.

From the tool's definition Append structured reverse-engineering evidence to a task artifact log

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_reverse_evidence Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_reverse_evidence": {
      "limits": [
        {
          "counter": "record_reverse_evidence_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 record_reverse_evidence

What does the record_reverse_evidence tool do? +

Append structured reverse-engineering evidence to a task artifact log. It is categorised as a Write tool in the JS Reverse MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_reverse_evidence? +

Register the JS Reverse MCP server in PolicyLayer and add a rule for record_reverse_evidence: 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 record_reverse_evidence? +

record_reverse_evidence is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit record_reverse_evidence? +

Yes. Add a rate_limit block to the record_reverse_evidence 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 record_reverse_evidence completely? +

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

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