Read the current value of an input, select, or textarea element.
AI agents call browser_input_value to retrieve information from Termux Browser Pilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the current value from a form element without creating, modifying, deleting, or executing any actions. It is a read-only operation that queries the state of the DOM. No data is changed and no external operations are triggered. The low severity reflects minimal risk even if misused—an attacker could only extract existing form values, not modify them or cause harm beyond information disclosure.
From the tool's definition Tool name 'browser_input_value' and description 'Read the current value of an input, select, or textarea element' clearly indicate retrieval of data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access browser_input_value gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Termux Browser Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_input_value:
{
"version": "1",
"default": "deny",
"tools": {
"browser_input_value": {}
}
}browser_input_value is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read the current value of an input, select, or textarea element. It is categorised as a Read tool in the Termux Browser Pilot MCP Server, which means it retrieves data without modifying state.
Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_input_value: 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 Termux Browser Pilot. Nothing to install.
browser_input_value is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the browser_input_value 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 browser_input_value. 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.
browser_input_value is provided by the Termux Browser Pilot MCP server (salviz/termux-browser-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Termux Browser Pilot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
148 Termux Browser Pilot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.