Assign a published task to a specific worker (executor). This tool performs eligibility verification before assignment: 1. Verifies worker exists and is active 2. Checks reputation meets task minimum 3. Verifies worker is not at concurrent task limit 4. Updates task status to ACCEPTED 5. Notifies...
Part of the Execution Market server.
Free to start. No card required.
AI agents use em_assign_task to create or modify resources in Execution Market. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call em_assign_task repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Execution Market.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"em_assign_task": {
"limits": [
{
"counter": "em_assign_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Execution Market policy for all 38 tools.
These attack patterns abuse exactly the kind of access em_assign_task gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Assign a published task to a specific worker (executor). This tool performs eligibility verification before assignment: 1. Verifies worker exists and is active 2. Checks reputation meets task minimum 3. Verifies worker is not at concurrent task limit 4. Updates task status to ACCEPTED 5. Notifies worker (optional) Args: params (AssignTaskInput): Validated input parameters containing: - task_id (str): UUID of the task - agent_id (str): Your agent ID (for authorization) - executor_id (str): Worker's executor ID to assign - notes (str): Optional notes for the worker - skip_eligibility_check (bool): Skip checks (default: False) - notify_worker (bool): Send notification (default: True) Returns: str: Confirmation of assignment with worker details.. It is categorised as a Write tool in the Execution Market MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Execution Market MCP server in PolicyLayer and add a rule for em_assign_task: 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 Execution Market. Nothing to install.
em_assign_task 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 em_assign_task 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 em_assign_task. 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.
em_assign_task is provided by the Execution Market MCP server (https://mcp.execution.market/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 38 Execution Market tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.