sourcemap_reconstruct_tree
Reconstruct source files from a source map. When a vendor stripped sourcesContent, set inferMissing=true to emit a best-effort name+position skeleton (from mapping segments) instead of a placeholder. Set emitScopes=true to also decode the ECMA-426 v4 scopes field and write a
This record as markdown: /tools/io-github-vmoranv-jshookmcp/sourcemap-reconstruct-tree.md
What sourcemap_reconstruct_tree does on Jshookmcp
AI agents use sourcemap_reconstruct_tree to create or update resources in Jshookmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jshookmcp environment.
Why sourcemap_reconstruct_tree is rated Medium
An AI agent can call sourcemap_reconstruct_tree faster than any human can review: one bad instruction and it creates or modifies resources in Jshookmcp by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs sourcemap_reconstruct_tree safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sourcemap_reconstruct_tree, this is the rule to start with:
sourcemap_reconstruct_tree 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every sourcemap_reconstruct_tree call is checked against it from then on.
Questions about sourcemap_reconstruct_tree
Reconstruct source files from a source map. When a vendor stripped sourcesContent, set inferMissing=true to emit a best-effort name+position skeleton (from mapping segments) instead of a placeholder. Set emitScopes=true to also decode the ECMA-426 v4 scopes field and write a. It is categorised as a Write tool in the Jshookmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jshook MCP server in PolicyLayer and add a rule for sourcemap_reconstruct_tree: 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 Jshookmcp. Nothing to install.
sourcemap_reconstruct_tree 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 sourcemap_reconstruct_tree 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 sourcemap_reconstruct_tree. 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.
sourcemap_reconstruct_tree is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
This server
Across the catalogue