Select an element on the page with Select tag
AI agents invoke playwright_select to trigger actions in RunAutomation MCP Server. 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.
This tool executes a browser automation action by selecting an element on a live web page. It falls under Execute because it triggers an external browser operation whose effects depend on the arguments provided (which element to select). While a simple selection may seem benign, in automated browser contexts it can trigger form submissions, change application state, or initiate downstream workflows.
From the tool's definition Select an element on the page with Select tag — triggers browser interaction (DOM selection action) via Playwright automation
Documented attack patterns abuse exactly the kind of access playwright_select gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RunAutomation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for playwright_select:
{
"version": "1",
"default": "deny",
"tools": {
"playwright_select": {
"limits": [
{
"counter": "playwright_select_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}playwright_select 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.
Select an element on the page with Select tag. It is categorised as a Execute tool in the RunAutomation MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the RunAutomation MCP Server MCP server in PolicyLayer and add a rule for playwright_select: 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 RunAutomation MCP Server. Nothing to install.
playwright_select 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 playwright_select 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 playwright_select. 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.
playwright_select is provided by the RunAutomation MCP Server MCP server (tayyabakmal1/runautomation-mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RunAutomation MCP 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.
91 RunAutomation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.