task_create
Adds a bounded task to a tenant-local run. Requires team:write. It records coordination state only and does not execute the task.
This record as markdown: /tools/hamza-agent-hub-252/task-create.md
What task_create does on Hamza Agent Hub 252
AI agents use task_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 task_create is rated Medium
Creates task metadata reversibly without execution or destructive side effects. Medium severity due to multi-tenant isolation risks.
From the tool's definition Adds a bounded task to a tenant-local run; records coordination state only.
Attacks that exploit this kind of access
The rule that runs task_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 task_create, this is the rule to start with:
task_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 task_create call is checked against it from then on.
Questions about task_create
Adds a bounded task to a tenant-local run. Requires team:write. It records coordination state only and does not execute the task. 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 task_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.
task_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 task_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 task_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.
task_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