Maps a generated code location back to the original source location using source maps.
AI agents call get_original_location to retrieve information from MCP JS Debugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation: it queries source map data to resolve code locations. There are no side effects, no code execution, no data modification, and no irreversible actions. It is purely informational retrieval used to support debugging workflows.
From the tool's definition The tool 'get_original_location' maps generated code locations to original source locations using source maps. This is a lookup/query operation that retrieves source location metadata without modifying state or executing code.
Attacks that exploit this kind of access
Maps a generated code location back to the original source location using source maps. It is categorised as a Read tool in the MCP JS Debugger MCP Server, which means it retrieves data without modifying state.
Register the MCP JS Debugger MCP server in PolicyLayer and add a rule for get_original_location: 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 MCP JS Debugger. Nothing to install.
get_original_location is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_original_location 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 get_original_location. 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.
get_original_location is provided by the MCP JS Debugger MCP server (johngrimes/mcp-js-debugger). 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 →