Export a local Node rebuild bundle from observed reverse-engineering evidence.
AI agents use export_rebuild_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.
This tool creates and exports a new Node.js bundle artifact based on reverse-engineering analysis. While it produces output rather than modifying existing source directly, the creation of a rebuild bundle represents a Write operation (artifact generation/creation).
From the tool's definition The tool performs an 'export' action that creates and outputs a 'rebuild bundle' from reverse-engineering evidence—a write operation that generates new artifacts.
Attacks that exploit this kind of access
Export a local Node rebuild bundle from observed reverse-engineering evidence. 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.
Register the JS Reverse MCP server in PolicyLayer and add a rule for export_rebuild_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.
export_rebuild_bundle 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 export_rebuild_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.
Set action: deny in the PolicyLayer policy for export_rebuild_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.
export_rebuild_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →