Check, uncheck, or toggle a checkbox or radio button.
AI agents invoke browser_check to trigger actions in Termux Browser Pilot. 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 performs an interactive browser action (checking/unchecking form controls) in a real browser. It's not merely reading data, nor is it creating/modifying persistent data in a reversible write sense — it executes a UI interaction that can trigger form submissions, enable/disable features, or change application state depending on the target element.
From the tool's definition 'Check, uncheck, or toggle a checkbox or radio button' — triggers browser UI interaction/action on a live browser automation session
Documented attack patterns abuse exactly the kind of access browser_check 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_check:
{
"version": "1",
"default": "deny",
"tools": {
"browser_check": {
"limits": [
{
"counter": "browser_check_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_check 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.
Check, uncheck, or toggle a checkbox or radio button. It is categorised as a Execute tool in the Termux Browser Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_check: 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_check 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 browser_check 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_check. 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_check 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.