Update resource limits and throttling configuration
AI agents use playwright_update_resource_limits to create or update resources in RunAutomation MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RunAutomation MCP Server environment.
This tool modifies configuration settings (resource limits and throttling) for browser sessions. It creates or modifies data reversibly — configuration changes can typically be reversed by updating them again. It does not execute code, delete data, or involve financial operations.
From the tool's definition Update resource limits and throttling configuration
Documented attack patterns abuse exactly the kind of access playwright_update_resource_limits 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_update_resource_limits:
{
"version": "1",
"default": "deny",
"tools": {
"playwright_update_resource_limits": {
"limits": [
{
"counter": "playwright_update_resource_limits_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} playwright_update_resource_limits stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update resource limits and throttling configuration. It is categorised as a Write tool in the RunAutomation MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RunAutomation MCP Server MCP server in PolicyLayer and add a rule for playwright_update_resource_limits: 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_update_resource_limits is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the playwright_update_resource_limits 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_update_resource_limits. 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_update_resource_limits 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.