Query element visibility, enabled, checked, and editable state.
AI agents call browser_element_state 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.
The tool queries the state of DOM elements (visibility, enabled, checked, editable) without side effects. This is a read-only inspection operation that retrieves information about the browser's current state. No data is modified, no code is executed, and no external operations are triggered. The low severity reflects that misuse would only expose information about page state, not enable harmful actions.
From the tool's definition Tool name 'browser_element_state' and description 'Query element visibility, enabled, checked, and editable state' indicate retrieval of element properties without modification or execution of actions.
Documented attack patterns abuse exactly the kind of access browser_element_state 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_element_state:
{
"version": "1",
"default": "deny",
"tools": {
"browser_element_state": {}
}
}browser_element_state 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.
Query element visibility, enabled, checked, and editable state. 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_element_state: 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_element_state 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_element_state 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_element_state. 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_element_state 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.