export_portable_bundle · JS Reverse MCP: Risk & Policy

WHAT IT DOES

What export_portable_bundle does on JS Reverse MCP

AI agents use export_portable_bundle 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 export_portable_bundle needs a policy

This tool creates or generates new bundled outputs from existing analysis artifacts, which constitutes data creation/modification (Write category). It doesn't execute arbitrary code, delete data, or trigger external financial operations.

From the tool's definition Tool produces 'portable single-file outputs' and 'extraction' implies writing aggregated analysis data to new files. The description emphasizes output generation and bundling of analysis artifacts rather than querying or reading existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_portable_bundle Rate-limited

export_portable_bundle 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": {
    "export_portable_bundle": {
      "limits": [
        {
          "counter": "export_portable_bundle_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 export_portable_bundle

What does the export_portable_bundle tool do? +

Collapse existing analysis artifacts into portable single-file outputs for pure extraction and local rebuild. 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 export_portable_bundle? +

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

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

Can I rate-limit export_portable_bundle? +

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

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

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