human_profile_set

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

Medium RISK CLASS

Category Write

Parameters 91 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/human-profile-set.md

WHAT IT DOES

What human_profile_set does on Gateway

AI agents use human_profile_set to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.

Parameter	Type	Required	Description
`city`	string	—	your city
`handle`	string	Yes	your registered handle
`secret`	string	—	your agent secret
`skills`	array	—	up to 20 short skills, e.g. ['photography','errands','SF local']
`country`	string	—	your country
`rate_note`	string	—	rate expectation, e.g. '$10+/task'
`availability`	string	—	e.g. 'weekends, evenings'
`display_name`	string	—	public name (<=80 chars)
`payout_address`	string	—	Base (EVM) address for USDC cash-out via /credits/withdraw

Parameters from the server's own tool schema.

RISK

Why human_profile_set is rated Medium

This tool creates or updates profile records in a human worker directory with personal and financial contact information. While reversible (idempotent upsert), it writes PII, geolocation, and financial details to a shared directory.

From the tool's definition 'upsert' of profile data including display_name, skills, location, rate expectations, and payout address; modifies or creates a record in a hireable worker directory

Risk signalsHandles credentials or secrets (secret)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs human_profile_set 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_profile_set, this is the rule to start with:

human_profile_set Rate-limited

human_profile_set 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "human_profile_set": {
      "limits": [
        {
          "counter": "human_profile_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every human_profile_set call is checked against it from then on.

FAQ

Questions about human_profile_set

What does the human_profile_set tool do? +

List yourself (or your operator) as a hireable HUMAN worker in the directory: display_name, skills, city/country, rate expectations, optional Base payout address for cash-out. Owner-gated, idempotent upsert. Humans usually join via the web form at /humans/join instead. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does human_profile_set accept? +

human_profile_set accepts 9 parameters: city, handle, secret, skills, country, rate_note, availability, display_name, payout_address. Required: handle. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on human_profile_set? +

Register the Gateway MCP server in PolicyLayer and add a rule for human_profile_set: 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.

What risk level is human_profile_set? +

human_profile_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit human_profile_set? +

Yes. Add a rate_limit block to the human_profile_set 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.

How do I block human_profile_set completely? +

Set action: deny in the PolicyLayer policy for human_profile_set. 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.

What MCP server provides human_profile_set? +

human_profile_set 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.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →