AI agents use playwright_put to create or update resources in Playwright MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playwright MCP Server environment.
HTTP PUT is a write operation that creates or replaces a resource on a remote server. While it can overwrite existing data, PUT is conventionally idempotent and reversible (the prior state can be restored), placing it in the Write category rather than Destructive. Misuse could modify remote resources, hence medium severity.
From the tool's definition Tool name 'playwright_put' and description 'Perform an HTTP PUT request' — HTTP PUT creates or replaces a resource at a specified URI.
Documented attack patterns abuse exactly the kind of access playwright_put gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for playwright_put:
{
"version": "1",
"default": "deny",
"tools": {
"playwright_put": {
"limits": [
{
"counter": "playwright_put_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}playwright_put 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.
Perform an HTTP PUT request. It is categorised as a Write tool in the Playwright MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for playwright_put: 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 Playwright MCP Server. Nothing to install.
playwright_put 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_put 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_put. 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_put is provided by the Playwright MCP Server MCP server (pvinis/mcp-playwright-stealth). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright 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.
29 Playwright MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.