Fill a form field by its ref ID with the given value. Returns updated page content.
AI agents invoke fill to trigger actions in WebControl. 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.
Filling a form field is a browser action that triggers external operations — it modifies the state of a live web page, potentially submitting data or triggering dynamic UI changes. This falls under Execute as it interacts with external systems through browser automation. The blast radius is medium because it can submit sensitive data or trigger workflows, but on its own it doesn't delete or move money.
From the tool's definition Fill a form field by its ref ID with the given value. Returns updated page content.
Attacks that exploit this kind of access
Fill a form field by its ref ID with the given value. Returns updated page content. It is categorised as a Execute tool in the WebControl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WebControl MCP server in PolicyLayer and add a rule for fill: 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 WebControl. Nothing to install.
fill 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 fill 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 fill. 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.
fill is provided by the WebControl MCP server (matansht/webcontrol). 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 →