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

browser_throttle_get

Get current network throttle configuration.

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

This record as markdown: /tools/salviz-termux-browser-pilot/browser-throttle-get.md

What browser_throttle_get does on Termux Browser Pilot

AI agents call browser_throttle_get 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_throttle_get is rated Low

This tool queries the current state of network throttling settings in the browser automation environment. It retrieves configuration data without modifying, executing, or deleting anything. This is a typical Read operation with minimal security risk—the information returned is about the browser's own settings, not sensitive user data or system state that could be exploited.

From the tool's definition Tool name 'browser_throttle_get' and description 'Get current network throttle configuration' indicate a retrieval operation with no side effects.

Questions about browser_throttle_get

What does the browser_throttle_get tool do? +

Get current network throttle configuration. It is categorised as a Read tool in the Termux Browser Pilot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_throttle_get? +

Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_throttle_get: 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_throttle_get? +

browser_throttle_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_throttle_get? +

Yes. Add a rate_limit block to the browser_throttle_get 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_throttle_get completely? +

Set action: deny in the PolicyLayer policy for browser_throttle_get. 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_throttle_get? +

browser_throttle_get 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.