register_instance_runtime
Register a local or managed ProAgentStore browser runtime for one of your private instances. Use this before run_instance_task for browser-capable agents.
This record as markdown: /tools/io-github-proagentstore-platform/register-instance-runtime.md
What register_instance_runtime does on ProAgentStore
AI agents use register_instance_runtime to create or update resources in ProAgentStore, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ProAgentStore environment.
Why register_instance_runtime is rated Medium
This tool registers (creates/enrolls) a runtime environment for a private instance, which is a reversible write operation. It sets up a configuration or association between a runtime and an instance but does not execute code, delete data, or involve financial transactions. The blast radius is medium since misconfiguring a runtime could affect subsequent agent tasks run on that instance.
From the tool's definition Register a local or managed ProAgentStore browser runtime for one of your private instances
Attacks that exploit this kind of access
The rule that runs register_instance_runtime 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 register_instance_runtime, this is the rule to start with:
register_instance_runtime stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 register_instance_runtime call is checked against it from then on.
Questions about register_instance_runtime
Register a local or managed ProAgentStore browser runtime for one of your private instances. Use this before run_instance_task for browser-capable agents. It is categorised as a Write tool in the ProAgentStore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for register_instance_runtime: 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.
register_instance_runtime is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the register_instance_runtime 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 register_instance_runtime. 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.
register_instance_runtime 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.
This server
Across the catalogue