ClearInput action, the position of the placeholder or text content in the target input field. If there is no content, locate the center of the input field.. Parameters: locate? (object) - The input field to be cleared
AI agents invoke ClearInput to trigger actions in Web Bridge. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
locate | object | — | The input field to be cleared |
web.url | string | — | URL to open in new tab (omit to use current page) |
web.aiActContext | string | — | Background knowledge passed to aiAct. Default: no extra context. |
web.waitAfterAction | number | — | Wait time in milliseconds after each action execution. Default: 300ms. |
web.replanningCycleLimit | integer | — | Maximum number of replanning cycles for aiAct. Default: model adapter default. |
web.screenshotShrinkFactor | number | — | Screenshot shrink factor before sending images to AI. Default: 1; high values may reduce recognition quality, especially on mobile. |
Parameters from the server's own tool schema.
ClearInput performs a browser/UI automation action that clears content from an input field. This is an Execute-category action as it triggers an external browser operation. While it modifies UI state, it is reversible (content can be re-entered), so Destructive is not warranted. Misuse could cause loss of unsaved user input in a web form, giving it medium severity.
From the tool's definition ClearInput action, the position of the placeholder or text content in the target input field... The input field to be cleared
Risk signalsAccepts URL/endpoint input (web.url) · High parameter count (11 properties)
Attacks that exploit this kind of access
ClearInput action, the position of the placeholder or text content in the target input field. If there is no content, locate the center of the input field.. Parameters: locate? (object) - The input field to be cleared. It is categorised as a Execute tool in the Web Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
ClearInput accepts 6 parameters: locate, web.url, web.aiActContext, web.waitAfterAction, web.replanningCycleLimit, web.screenshotShrinkFactor. The full parameter table on this page comes from the server's own tool schema.
Register the Web Bridge MCP server in PolicyLayer and add a rule for ClearInput: 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 Bridge. Nothing to install.
ClearInput 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 ClearInput 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 ClearInput. 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.
ClearInput is provided by the Web Bridge MCP server (@midscene/web-bridge-mcp). 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 →