Get text content from an element inside shadow DOM.
AI agents call browser_shadow_text 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.
This tool retrieves text content from DOM elements, which is a read-only operation with no side effects. It queries the browser's DOM structure to extract data, similar to a search or get operation. The fact that it targets shadow DOM does not change the fundamental nature of the operation as a non-destructive data retrieval.
From the tool's definition Tool name 'browser_shadow_text' and description 'Get text content from an element inside shadow DOM' indicate a retrieval operation with no modification or execution of code.
Documented attack patterns abuse exactly the kind of access browser_shadow_text 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_shadow_text:
{
"version": "1",
"default": "deny",
"tools": {
"browser_shadow_text": {}
}
}browser_shadow_text 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.
Get text content from an element inside shadow DOM. 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_shadow_text: 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_shadow_text 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_shadow_text 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_shadow_text. 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_shadow_text 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.