run_instance_task
Create a task on the registered local or managed browser runtime for a private instance. The PAGS brain stays in control; the local ProAgentStore runner executes browser capabilities through the relay.
This record as markdown: /tools/io-github-proagentstore-platform/run-instance-task.md
What run_instance_task does on ProAgentStore
AI agents invoke run_instance_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 run_instance_task is rated High
Triggers external browser operations whose effects depend on task arguments; local execution relay amplifies blast radius.
From the tool's definition Create a task on registered browser runtime; executes browser capabilities through relay.
Attacks that exploit this kind of access
The rule that runs run_instance_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_instance_task, this is the rule to start with:
run_instance_task stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every run_instance_task call is checked against it from then on.
Questions about run_instance_task
Create a task on the registered local or managed browser runtime for a private instance. The PAGS brain stays in control; the local ProAgentStore runner executes browser capabilities through the relay. 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.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for run_instance_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.
run_instance_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_instance_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.
Set action: deny in the PolicyLayer policy for run_instance_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.
run_instance_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.
Across the catalogue