New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

sourcemap_lookup

Resolve generated code position to original source (default), or — when originalSource is supplied — resolve original source:line:column back to the generated position. Supports indexed (sectioned) source maps transparently.

SERVERJshookmcp SOURCE@jshookmcp/jshook
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/sourcemap-lookup.md

What sourcemap_lookup does on Jshookmcp

AI agents call sourcemap_lookup to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why sourcemap_lookup is rated Low

Tool queries source map data without creating, modifying, or deleting any code or files.

From the tool's definition Resolve generated code position to original source, lookup, no modification

Questions about sourcemap_lookup

What does the sourcemap_lookup tool do? +

Resolve generated code position to original source (default), or — when originalSource is supplied — resolve original source:line:column back to the generated position. Supports indexed (sectioned) source maps transparently. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sourcemap_lookup? +

Register the Jshook MCP server in PolicyLayer and add a rule for sourcemap_lookup: 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.

What risk level is sourcemap_lookup? +

sourcemap_lookup is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sourcemap_lookup? +

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

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Jshook's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.