set_instance_runner_node
Pin one instance to a specific machine, so its runner calls (chat tools, apply, coding) route there — and MOVE it there in the same call: when that machine\
This record as markdown: /tools/io-github-proagentstore-platform/set-instance-runner-node.md
What set_instance_runner_node does on ProAgentStore
AI agents invoke set_instance_runner_node 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 set_instance_runner_node is rated High
Reroutes and migrates a running instance to a specific machine, triggering external infrastructure changes.
From the tool's definition Pin instance to specific machine, MOVE it there in same call
Attacks that exploit this kind of access
The rule that runs set_instance_runner_node 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 set_instance_runner_node, this is the rule to start with:
set_instance_runner_node 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 set_instance_runner_node call is checked against it from then on.
Questions about set_instance_runner_node
Pin one instance to a specific machine, so its runner calls (chat tools, apply, coding) route there — and MOVE it there in the same call: when that machine\. 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 set_instance_runner_node: 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.
set_instance_runner_node 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 set_instance_runner_node 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 set_instance_runner_node. 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.
set_instance_runner_node 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