instance_runner_node

Read which machine ONE instance is pinned to, and which machines it could be pinned to.

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/instance-runner-node.md

WHAT IT DOES

What instance_runner_node does on ProAgentStore

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

RISK

Why instance_runner_node is rated Low

Tool retrieves infrastructure configuration data without modifying or executing operations.

From the tool's definition Read which machine ONE instance is pinned to, and which machines it could be pinned to.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs 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 instance_runner_node, this is the rule to start with:

instance_runner_node Allowed

instance_runner_node is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "instance_runner_node": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every instance_runner_node call is checked against it from then on.

FAQ

Questions about instance_runner_node

What does the instance_runner_node tool do? +

Read which machine ONE instance is pinned to, and which machines it could be pinned to. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on instance_runner_node? +

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

What risk level is instance_runner_node? +

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

Can I rate-limit instance_runner_node? +

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

How do I block instance_runner_node completely? +

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

What MCP server provides instance_runner_node? +

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.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →