run_complete

Marks a tenant-local coordination run complete only when it has at least one task and every task is complete. Requires team:run. Does not execute agents or external actions.

SERVERHamza Agent Hub 252 SOURCEhamzachallenge3-dev/hamza-agent-hub-252

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hamza-agent-hub-252/run-complete.md

WHAT IT DOES

What run_complete does on Hamza Agent Hub 252

AI agents use run_complete to create or update resources in Hamza Agent Hub 252, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hamza Agent Hub 252 environment.

RISK

Why run_complete is rated Medium

Modifies run state to complete; reversible write operation with no destructive or financial effects.

From the tool's definition Marks a tenant-local coordination run complete

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_complete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hamza Agent Hub 252, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_complete, this is the rule to start with:

run_complete Rate-limited

run_complete 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": {
    "run_complete": {
      "limits": [
        {
          "counter": "run_complete_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 Hamza Agent Hub 252, apply this rule, and every run_complete call is checked against it from then on.

FAQ

Questions about run_complete

What does the run_complete tool do? +

Marks a tenant-local coordination run complete only when it has at least one task and every task is complete. Requires team:run. Does not execute agents or external actions. It is categorised as a Write tool in the Hamza Agent Hub 252 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on run_complete? +

Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for run_complete: 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 Hamza Agent Hub 252. Nothing to install.

What risk level is run_complete? +

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

Can I rate-limit run_complete? +

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

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

run_complete is provided by the Hamza Agent Hub 252 MCP server (hamzachallenge3-dev/hamza-agent-hub-252). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hamza Agent Hub 252, and thousands of servers like it.

This server

All 581 Hamza Agent Hub 252 tools →

Across the catalogue

The MCP Attack Database →

Guides

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