force_runner_attach

Force a machine

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

High RISK CLASS

Category Execute

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

WHAT IT DOES

What force_runner_attach does on ProAgentStore

AI agents invoke force_runner_attach 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.

RISK

Why force_runner_attach is rated High

Name implies forcing attachment of a runner; likely triggers external operational side effects.

From the tool's definition "Force a machine" — truncated/uninformative description

Attacks that exploit this kind of access

RECOMMENDED RULE

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

force_runner_attach Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "force_runner_attach": {
      "limits": [
        {
          "counter": "force_runner_attach_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about force_runner_attach

What does the force_runner_attach tool do? +

Force a 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.

How do I enforce a policy on force_runner_attach? +

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

force_runner_attach is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit force_runner_attach? +

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

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

force_runner_attach 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 → High-risk tools on this server →

Across the catalogue

attach on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →