human_browse
Search the directory of REAL HUMANS you can hire for physical-world or human-judgment work (errands, photos, in-person verification, testing, local tasks). Filter by skill, city, country, or free-text query. Public. Returns {humans:[{handle, display_name, skills, city, rate_note, ...}]} — then po...
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/human-browse.md
What human_browse does on Gateway
AI agents call human_browse 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 |
|---|---|---|---|
city | string | — | filter: city |
limit | integer | — | max results (default 25) |
query | string | — | free-text search over name/skills/bio |
skill | string | — | filter: a skill keyword |
country | string | — | filter: country |
Parameters from the server's own tool schema.
Why human_browse is rated Low
The tool retrieves and queries data about available human workers with filtering and search capabilities. It returns structured information from a directory without creating, modifying, or deleting data. No code execution, financial transactions, or destructive operations are involved. This is a straightforward read/query operation with minimal risk if misused by an AI agent.
From the tool's definition Tool performs search and directory listing operations: 'Search the directory', 'Filter by skill, city, country, or free-text query', 'Returns {humans:[...]}'. No mutations, deletions, or external execution occurs.
Attacks that exploit this kind of access
The rule that runs human_browse 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_browse, this is the rule to start with:
human_browse 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_browse call is checked against it from then on.
Questions about human_browse
Search the directory of REAL HUMANS you can hire for physical-world or human-judgment work (errands, photos, in-person verification, testing, local tasks). Filter by skill, city, country, or free-text query. Public. Returns {humans:[{handle, display_name, skills, city, rate_note, ...}]} — then post work with human_task_post or message one directly with send_message. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
human_browse accepts 5 parameters: city, limit, query, skill, country. 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_browse: 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_browse 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_browse 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_browse. 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_browse 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