Get all JavaScript sources loaded in the current page. Useful for understanding code structure before setting breakpoints.
AI agents call get_script_sources to retrieve information from Chrome DevTools MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though get_script_sources only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Get all JavaScript sources loaded in the current page. Useful for understanding code structure before setting breakpoints. It is categorised as a Read tool in the Chrome DevTools MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chrome DevTools MCP Server MCP server in PolicyLayer and add a rule for get_script_sources: 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 Chrome DevTools MCP Server. Nothing to install.
get_script_sources 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_sources 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_sources. 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_sources is provided by the Chrome DevTools MCP Server MCP server (xrealsys/chrome-devtool-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.