Retrieves the source code for a script.
AI agents call get_script_source 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 retrieval of source code from a debugging session. It does not execute code, modify data, delete resources, or commit financial obligations. While it provides access to source code during debugging, this is expected behavior within a debugger context and poses only minimal risk of misuse—an AI agent using this tool can only view source, not alter execution or system state.
From the tool's definition Tool name 'get_script_source' and description 'Retrieves the source code for a script' indicate a query operation that fetches data without modification or side effects.
Attacks that exploit this kind of access
Retrieves the source code for a script. 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_script_source: 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_script_source 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_script_source 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_script_source. 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_script_source 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 →