Inject JavaScript libraries into the page
AI agents invoke inject_script_library to trigger actions in Pydoll. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Injecting JavaScript libraries into a page constitutes arbitrary code execution within the browser context. This can modify page behavior, exfiltrate data, intercept credentials, or perform any action the page's JavaScript context permits. The blast radius is high as a misused injection could compromise the entire page environment and any sensitive data within it.
From the tool's definition Inject JavaScript libraries into the page
Documented attack patterns abuse exactly the kind of access inject_script_library gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pydoll, and nothing reaches the server without passing your rules. This is the rule we recommend for inject_script_library:
{
"version": "1",
"default": "deny",
"tools": {
"inject_script_library": {
"limits": [
{
"counter": "inject_script_library_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}inject_script_library stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Inject JavaScript libraries into the page. It is categorised as a Execute tool in the Pydoll MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pydoll MCP server in PolicyLayer and add a rule for inject_script_library: 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 Pydoll. Nothing to install.
inject_script_library is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the inject_script_library 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 inject_script_library. 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.
inject_script_library is provided by the Pydoll MCP server (jinsongroh/pydoll-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pydoll, 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.
57 Pydoll tools catalogued and risk-classified — across an index of 43,000+ MCP servers.