runner_setup

Read the setup checklist for a coding agent that runs on your own machine (e.g. a

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

Medium RISK CLASS

Category Write

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/runner-setup.md

WHAT IT DOES

What runner_setup does on ProAgentStore

AI agents use runner_setup 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.

RISK

Why runner_setup is rated Medium

An AI agent can call runner_setup faster than any human can review: one bad instruction and it creates or modifies resources in ProAgentStore by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

runner_setup Rate-limited

runner_setup 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "runner_setup": {
      "limits": [
        {
          "counter": "runner_setup_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about runner_setup

What does the runner_setup tool do? +

Read the setup checklist for a coding agent that runs on your own machine (e.g. a. 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.

How do I enforce a policy on runner_setup? +

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

runner_setup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit runner_setup? +

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

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

runner_setup 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

Govern customer-ops agents →Argument validation →Scoped token →