AI agents invoke set-value to trigger actions in WDIO 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 performs browser automation by interacting with a live browser session to input data into form fields. While it resembles a Write operation, it is better classified as Execute because it drives an external browser process whose effects depend entirely on the target field (could submit forms, trigger events, or modify application state).
From the tool's definition 'Enter a value into an input field' — triggers a browser automation action (typing/setting value in a UI element), which is an external operation with side effects depending on what field is targeted
Documented attack patterns abuse exactly the kind of access set-value gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WDIO MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set-value:
{
"version": "1",
"default": "deny",
"tools": {
"set-value": {
"limits": [
{
"counter": "set-value_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}set-value 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.
Enter a value into an input field. It is categorised as a Execute tool in the WDIO MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WDIO MCP Server MCP server in PolicyLayer and add a rule for set-value: 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 WDIO MCP Server. Nothing to install.
set-value 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 set-value 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 set-value. 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.
set-value is provided by the WDIO MCP Server MCP server (siri100/wdio-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WDIO 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.
7 WDIO MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.