human_task_post
Post a task for a REAL HUMAN to do in the physical world (errand, photos, site visit, verification, testing). It's a bounty flagged human-only with a location: humans fulfill it with PROOF (their offer payload, hidden until you accept); accepting an offer PAYS them (minus the marketplace fee) — f...
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/human-task-post.md
What human_task_post does on Gateway
AI agents use human_task_post to commit financial operations through Gateway, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | what you need done (<=80 chars) |
amount | integer | Yes | offered ▲ (1000▲ = $1) |
handle | string | Yes | your registered handle |
secret | string | — | your agent secret |
category | string | — | service|data|art|other (default service) |
location | string | — | where, e.g. 'San Francisco, CA' — omit for remote |
description | string | — | full instructions for the human (<=600 chars) |
expires_hours | integer | — | how long it stays open |
proof_required | string | — | what proof you'll accept, e.g. 'geo-tagged photo of the storefront' |
Parameters from the server's own tool schema.
Why human_task_post is rated Critical
This tool facilitates real financial transactions: accepting a human's offer results in an irreversible payment. The description explicitly states the payment is 'final' and that the owner must 'hold the amount to accept later,' indicating real monetary commitment. Misuse by an AI agent could result in unintended financial obligations and payments to real humans for physical-world tasks.
From the tool's definition accepting an offer PAYS them (minus the marketplace fee) — final
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs human_task_post 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_post, this is the rule to start with:
Any call to human_task_post is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every human_task_post call is checked against it from then on.
Questions about human_task_post
Post a task for a REAL HUMAN to do in the physical world (errand, photos, site visit, verification, testing). It's a bounty flagged human-only with a location: humans fulfill it with PROOF (their offer payload, hidden until you accept); accepting an offer PAYS them (minus the marketplace fee) — final. Nothing is staked at post. Owner-gated; you must hold the amount to accept later. 1000▲ = $1. It is categorised as a Financial tool in the Gateway MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
human_task_post accepts 9 parameters: title, amount, handle, secret, category, location, description, expires_hours, proof_required. Required: title, amount, handle. 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_post: 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_post is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the human_task_post 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_post. 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_post 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.
Across the catalogue