Set the value of an input / textarea / contenteditable matching the
AI agents invoke dom_type to trigger actions in Hermes Computer Use. 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 interacts with a live browser by injecting text into form fields, which can trigger form submissions, search queries, login attempts, or other actions with real-world consequences. It is part of a browser automation server designed to evade anti-bot detection, amplifying misuse risk. The action itself is an Execute-level browser interaction rather than a simple write to a data store.
From the tool's definition 'dom_type' sets the value of an input/textarea/contenteditable element in a real Chrome browser driven by OS-level mouse/keyboard automation
Attacks that exploit this kind of access
Set the value of an input / textarea / contenteditable matching the. It is categorised as a Execute tool in the Hermes Computer Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hermes Computer Use MCP server in PolicyLayer and add a rule for dom_type: 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 Hermes Computer Use. Nothing to install.
dom_type 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 dom_type 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 dom_type. 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.
dom_type is provided by the Hermes Computer Use MCP server (noah3521/hermes-computer-use). 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 →