New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

browser_attr_set

Set an attribute on an element.

SERVERTermux Browser Pilot SOURCEsalviz/termux-browser-pilot
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/salviz-termux-browser-pilot/browser-attr-set.md

What browser_attr_set does on Termux Browser Pilot

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.

Why browser_attr_set is rated High

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

Questions about browser_attr_set

What does the browser_attr_set tool do? +

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.

How do I enforce a policy on browser_attr_set? +

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.

What risk level is browser_attr_set? +

browser_attr_set is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_attr_set? +

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.

How do I block browser_attr_set completely? +

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.

What MCP server provides browser_attr_set? +

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.

More on Termux Browser Pilot, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Termux Browser Pilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.