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

get_setup_status

Return extension path, bridge ports, and connection status for setup/diagnostics.

SERVERAgent Browser SOURCE335234131/agent-browser-mcp
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/335234131-agent-browser-mcp/get-setup-status.md

What get_setup_status does on Agent Browser

AI agents call get_setup_status to retrieve information from Agent Browser without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_setup_status is rated Low

This tool queries and returns system configuration and connection status information. It is a diagnostic/status check operation with no capability to modify state, execute code, delete data, or trigger external operations. The data returned (extension path, ports, connection status) are read-only diagnostic facts about the current setup.

From the tool's definition Tool name 'get_setup_status' and description 'Return extension path, bridge ports, and connection status for setup/diagnostics' indicate retrieval of configuration and diagnostic information only. No modification, execution, or side effects are performed.

Questions about get_setup_status

What does the get_setup_status tool do? +

Return extension path, bridge ports, and connection status for setup/diagnostics. It is categorised as a Read tool in the Agent Browser MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_setup_status? +

Register the Agent Browser MCP server in PolicyLayer and add a rule for get_setup_status: 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 Agent Browser. Nothing to install.

What risk level is get_setup_status? +

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

Can I rate-limit get_setup_status? +

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

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

get_setup_status is provided by the Agent Browser MCP server (335234131/agent-browser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Agent Browser, 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 Agent Browser'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.