Get all JavaScript code from the current page
AI agents call getScripts to retrieve information from PlayMCP Browser Automation Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves JavaScript source code from a webpage for inspection purposes. It performs a read-only query operation that returns information about the page without modifying state, executing arbitrary code, or causing side effects. While the retrieved JavaScript code itself might contain sensitive information, the tool's function is purely informational retrieval.
From the tool's definition Tool name 'getScripts' and description 'Get all JavaScript code from the current page' indicate retrieval of existing data with no modification or execution of code.
Documented attack patterns abuse exactly the kind of access getScripts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PlayMCP Browser Automation Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getScripts:
{
"version": "1",
"default": "deny",
"tools": {
"getScripts": {}
}
}getScripts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all JavaScript code from the current page. It is categorised as a Read tool in the PlayMCP Browser Automation Server MCP Server, which means it retrieves data without modifying state.
Register the PlayMCP Browser Automation Server MCP server in PolicyLayer and add a rule for getScripts: 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 PlayMCP Browser Automation Server. Nothing to install.
getScripts 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 getScripts 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 getScripts. 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.
getScripts is provided by the PlayMCP Browser Automation Server MCP server (jomon003/playmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PlayMCP Browser Automation Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 PlayMCP Browser Automation Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.