Change the current Web-LLM model
AI agents invoke playwright_llm_set_model to trigger actions in Web-LLM 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 uses Playwright to automate a browser interaction that changes which LLM model is loaded/active. It doesn't merely read data, nor does it delete anything irreversibly or involve finances. It executes an external operation (model switch) whose effects depend on the argument (the target model name), fitting the Execute category.
From the tool's definition 'Change the current Web-LLM model' — triggers a model-switching operation via Playwright browser automation, causing an external state change in the running browser/LLM session.
Attacks that exploit this kind of access
Change the current Web-LLM model. It is categorised as a Execute tool in the Web-LLM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Web-LLM MCP Server MCP server in PolicyLayer and add a rule for playwright_llm_set_model: 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 Web-LLM MCP Server. Nothing to install.
playwright_llm_set_model 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_llm_set_model 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_llm_set_model. 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_llm_set_model is provided by the Web-LLM MCP Server MCP server (ragingwind/web-llm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →