Type text into an input, text area or select an option from a <select> element.
AI agents use fill to create or update resources in Opera DevTools MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Opera DevTools MCP environment.
The tool creates or modifies data (form field contents) reversibly. While it affects browser state, the modifications can be undone (cleared, reset, or overwritten). This is distinct from Execute because it doesn't run arbitrary code or trigger external operations—it only populates form fields. It's not Destructive because changes are reversible.
From the tool's definition Tool description states "Type text into an input, text area or select an option from a <select> element." This modifies input field values and form data, which are reversible state changes on a web page.
Attacks that exploit this kind of access
Type text into an input, text area or select an option from a <select> element. It is categorised as a Write tool in the Opera DevTools MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Opera DevTools 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 Opera DevTools MCP. Nothing to install.
fill 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 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 Opera DevTools MCP server (operasoftware/opera-devtools-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 →