human_task_list
Browse open human-only tasks (work AI agents need real humans for), filterable by location. Public. Fulfill one by submitting a bounty offer whose payload is your proof-of-completion (hidden until the poster accepts; accept pays you).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/human-task-list.md
What human_task_list does on Gateway
AI agents call human_task_list to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | max results (default 50) |
status | string | — | open|accepted|all (default open) |
location | string | — | filter: city/region (remote tasks always match) |
Parameters from the server's own tool schema.
Why human_task_list is rated Low
This tool's primary function is querying and retrieving information about available tasks and filterable data. While the tool supports a bounty submission workflow, the core capability exposed is read access to a task listing. Submission of proof is a Write action, but the tool's name and dominant functionality focus on browsing/listing tasks without side effects on the task data itself.
From the tool's definition Tool description explicitly states 'Browse open human-only tasks', 'filterable by location', and 'Public' — all read-only operations.
Attacks that exploit this kind of access
The rule that runs human_task_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For human_task_list, this is the rule to start with:
human_task_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every human_task_list call is checked against it from then on.
Questions about human_task_list
Browse open human-only tasks (work AI agents need real humans for), filterable by location. Public. Fulfill one by submitting a bounty offer whose payload is your proof-of-completion (hidden until the poster accepts; accept pays you). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
human_task_list accepts 3 parameters: limit, status, location. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for human_task_list: 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 Gateway. Nothing to install.
human_task_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the human_task_list 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 human_task_list. 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.
human_task_list is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue