AI agents invoke browser_attr_set 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.
Setting an attribute on a DOM element modifies the live state of a webpage in a browser session. This is a write-like action that can trigger side effects (e.g., changing href, src, event handlers, or form actions), potentially enabling injection or manipulation of browser behavior. It goes beyond simple data writes because it directly manipulates browser/DOM state and can influence subsequent execution.
From the tool's definition Set an attribute on an element
Documented attack patterns abuse exactly the kind of access browser_attr_set 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_attr_set:
{
"version": "1",
"default": "deny",
"tools": {
"browser_attr_set": {
"limits": [
{
"counter": "browser_attr_set_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_attr_set 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.
Set an attribute on an element. 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_attr_set: 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_attr_set 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_attr_set 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_attr_set. 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_attr_set 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.