Input text into an interactive element at the specified index. Args: index (int): The index of the element to input text into text (str): The text to input has_sensitive_data (bool, optional): Whether the text is sensitive data. Defaults to False. Returns: str: A message confirming the text input
AI agents invoke input_text to trigger actions in Mcp Browser 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 types text into browser UI elements (forms, inputs, etc.), which constitutes a browser action with external side effects. The effects depend entirely on what element is targeted and what text is input — ranging from benign search queries to submitting credentials, financial forms, or triggering workflows.
From the tool's definition Input text into an interactive element at the specified index / has_sensitive_data (bool, optional): Whether the text is sensitive data
Documented attack patterns abuse exactly the kind of access input_text gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Browser Use, and nothing reaches the server without passing your rules. This is the rule we recommend for input_text:
{
"version": "1",
"default": "deny",
"tools": {
"input_text": {
"limits": [
{
"counter": "input_text_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}input_text 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.
Input text into an interactive element at the specified index. Args: index (int): The index of the element to input text into text (str): The text to input has_sensitive_data (bool, optional): Whether the text is sensitive data. Defaults to False. Returns: str: A message confirming the text input. It is categorised as a Execute tool in the Mcp Browser Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Browser Use MCP server in PolicyLayer and add a rule for input_text: 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 Mcp Browser Use. Nothing to install.
input_text 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 input_text 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 input_text. 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.
input_text is provided by the Mcp Browser Use MCP server (vinayak-mehta/mcp-browser-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Mcp Browser Use tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 Mcp Browser Use tools catalogued and risk-classified — across an index of 42,500+ MCP servers.