Get the full source code of a script by scriptId or URL
AI agents call source_get_script to retrieve information from CDP-MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves source code content from the target browser context. While it is fundamentally a read operation, the severity is elevated to 'medium' rather than 'low' because: (1) source code may contain sensitive logic, credentials, or proprietary algorithms; (2) it operates within a low-level browser debugging context where an agent could systematically exfiltrate application code; (3) the Chrome DevTools…
From the tool's definition Tool name 'source_get_script' and description 'Get the full source code of a script by scriptId or URL' indicate retrieval of data with no modification or execution.
Attacks that exploit this kind of access
Get the full source code of a script by scriptId or URL. It is categorised as a Read tool in the CDP-MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CDP-MCP Server MCP server in PolicyLayer and add a rule for source_get_script: 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 CDP-MCP Server. Nothing to install.
source_get_script 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 source_get_script 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 source_get_script. 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.
source_get_script is provided by the CDP-MCP Server MCP server (jekyll-001/cdp-mcp-server). 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 →