run_create
Creates a budgeted coordination run for an existing team. Requires team:run. This records the run but does not contact external systems or spend provider credits.
This record as markdown: /tools/hamza-agent-hub-252/run-create.md
What run_create does on Hamza Agent Hub 252
AI agents use run_create 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.
Why run_create is rated Medium
Creates a new run record reversibly; no external systems contacted or funds spent.
From the tool's definition Creates a budgeted coordination run for an existing team
Attacks that exploit this kind of access
The rule that runs run_create 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_create, this is the rule to start with:
run_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hamza Agent Hub 252, apply this rule, and every run_create call is checked against it from then on.
Questions about run_create
Creates a budgeted coordination run for an existing team. Requires team:run. This records the run but does not contact external systems or spend provider credits. 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.
Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for run_create: 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.
run_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the run_create 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.
Set action: deny in the PolicyLayer policy for run_create. 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.
run_create 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.
More on Hamza Agent Hub 252, and thousands of servers like it.
This server
Across the catalogue