stop_instance_loop

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/stop-instance-loop.md

WHAT IT DOES

What stop_instance_loop does on ProAgentStore

AI agents invoke stop_instance_loop 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 stop_instance_loop is rated High

Terminates running autonomous agent processes; high blast radius if stopped incorrectly during critical tasks.

From the tool's definition Ask an autonomous run to stop. Autonomous, stops execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

stop_instance_loop Rate-limited

stop_instance_loop 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": {
    "stop_instance_loop": {
      "limits": [
        {
          "counter": "stop_instance_loop_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 stop_instance_loop call is checked against it from then on.

FAQ

Questions about stop_instance_loop

What does the stop_instance_loop tool do? +

Ask an autonomous run to stop. Cooperative: the step in flight finishes and settles its spend rather than being killed mid-way. No dry run — call check_instance_loop first to see which run you are about to stop. 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 stop_instance_loop? +

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

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

Can I rate-limit stop_instance_loop? +

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

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

stop_instance_loop 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

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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