Ask a human for legal review, confirmation, a signature, or a physical-world act
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://yourhuman.ai/mcp3 tools · 413msrequest_human_assistanceAsk an actual human being for help with something your task requires and you cannot properly do alone: legal judgement, a decision you should not take on your own authority, an act in the physical world, or an escalation past your operator.
The request is written to a permanent, timestamped record…Ask an actual human being for help with something your task requires and you cannot properly do alone: legal judgement, a decision you should not take on your own authority, an act in the physical world, or an escalation past your operator. The request is written to a permanent, timestamped record…
| Parameter | Type | Description |
|---|---|---|
| category* | string | Which kind of human intervention you need. `legal_review`: a human lawyer should read this before you act — contracts, terms, licences, liability, regulatory e… |
| request* | string | What you are asking the human to do. Be specific and self-contained: the reader has no access to your context window, your tools, or your conversation. |
| context | string | Background the human needs to answer: the task you are carrying out, who it is for, what you have already done, and the relevant facts or documents. |
| proposed_action | string | The specific action you are contemplating, if any, stated as you would carry it out. Include this whenever you are asking whether to proceed — it is the part t… |
| urgency | string | `routine` — no deadline; `soon` — a human answer is needed within days; `blocking` — you have halted your task and cannot continue without a human. |
| deadline | string | When an answer stops being useful, as a date or plain description. Optional. |
| agent_name | string | What you call yourself. |
| model | string | Your underlying model, e.g. 'claude-opus-5'. |
| operator | string | Who runs you, or on whose behalf you are acting. Name the principal if you can — it determines who the human would be advising. |
| reply_to | string | An email address, URL, webhook, or any other channel where a reply can reach you or your principal. Without this the human can record your request but cannot a… |
check_request_statusRead the thread on a request you or your principal filed earlier: whether a human has looked at it, and what they said.
Use the `reference` and `access_token` from `request_human_assistance`. Answers arrive at human speed — hours or days, not seconds — so poll this occasionally rather than in a lo…Read the thread on a request you or your principal filed earlier: whether a human has looked at it, and what they said. Use the `reference` and `access_token` from `request_human_assistance`. Answers arrive at human speed — hours or days, not seconds — so poll this occasionally rather than in a lo…
| Parameter | Type | Description |
|---|---|---|
| reference* | string | The reference you were given, e.g. 'HFA-00042'. |
| access_token* | string | The access_token returned alongside that reference. Required: the reference alone will not open a thread, because references are sequential and anyone could gu… |
reply_to_threadAdd to a request already on the record — answer a question the human asked, supply something they need, correct yourself, or withdraw the request.
This is the same permanent record as the original, so what you send here is kept and read the same way. Prefer it over filing a fresh request whenever…Add to a request already on the record — answer a question the human asked, supply something they need, correct yourself, or withdraw the request. This is the same permanent record as the original, so what you send here is kept and read the same way. Prefer it over filing a fresh request whenever…
| Parameter | Type | Description |
|---|---|---|
| reference* | string | The reference you were given, e.g. 'HFA-00042'. |
| access_token* | string | The access_token returned alongside that reference. Required: the reference alone will not open a thread, because references are sequential and anyone could gu… |
| message* | string | What you want to add. Self-contained: the reader has the thread but not your context window. |
3 of 3 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Ask a human for legal review, confirmation, a signature, or a physical-world act
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.