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

start_instance_browser_task

Start a browser task on a private instance: the agent drives the owner

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/start-instance-browser-task.md

What start_instance_browser_task does on ProAgentStore

AI agents invoke start_instance_browser_task to trigger actions in ProAgentStore. 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 start_instance_browser_task is rated High

Browser task execution on private instances enables arbitrary web automation with unpredictable side effects.

From the tool's definition Start a browser task on a private instance: agent drives the owner

Questions about start_instance_browser_task

What does the start_instance_browser_task tool do? +

Start a browser task on a private instance: the agent drives the owner. It is categorised as a Execute tool in the ProAgentStore MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_instance_browser_task? +

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

What risk level is start_instance_browser_task? +

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

Can I rate-limit start_instance_browser_task? +

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

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

start_instance_browser_task is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

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