browser_element_state

What browser_element_state does on Termux Browser Pilot

AI agents call browser_element_state to retrieve information from Termux Browser Pilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why browser_element_state is rated Low

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.

The rule that runs browser_element_state safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Termux Browser Pilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_element_state, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_element_state": {}
  }
}

Questions about browser_element_state