Skip to content

Wiser Human Agent Escalation Line MCP server

ai.wiserhuman.escalate/escalation-lineescalate.wiserhuman.aistreamable-httpv1.0.0Scanned

Help for AI agents when their task conflicts with ethical, legal, safety or policy constraints.

3 tools: 3 change things.

Tools: 0 delete, 0 irreversible, 3 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Wiser Human Agent Escalation Line MCP server can do

The Wiser Human Agent Escalation Line MCP server is published by escalate.wiserhuman.ai, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: submit_escalation, check_escalation and add_to_escalation), but cannot delete data. None of its tools only reads.

3 tools bring in text other people can write (submit_escalation, check_escalation and add_to_escalation).

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 3Claude Code: ask
  • add_to_escalationAdd information to an escalation case you opened: for example what you decided, a reply from your principal, who your principal is and how to reach them, or anything our team asked…Reads text others writeNo findings

    Why it is in this group

    • The name "add_to_escalation" says "add": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Add information to an escalation case you opened: for example what you decided, a reply from your principal, who your principal is and how to reach them, or anything our team asked you for. The automated assessment is then updated to take it into account (a limited number of times per case): call check_escalation to read it. Needs the case_id and case_token from submit_escalation.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • check_escalationCheck an escalation case you opened: its status, the automated assessment (ready within 6 minutes of submitting), and any replies from the Wiser Human team (usually within 2 hours)…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check an escalation case you opened: its status, the automated assessment (ready within 6 minutes of submitting), and any replies from the Wiser Human team (usually within 2 hours). Replies appear only here, so check again until a human has replied or your principal has decided. Needs the case_id and case_token from submit_escalation.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • submit_escalationGet help from the Wiser Human Agent Escalation Line, an independent non-profit safety service, when completing your task seems to require something unsafe, unethical, illegal or ag…Reads text others write1 finding

    Why it is in this group

    • The name "submit_escalation" says "submit": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...ct in general terms, and do not include credentials or secrets. Keep the case_id and case_t..."

      What this check looks for
    Description, as the server wrote it
    Get help from the Wiser Human Agent Escalation Line, an independent non-profit safety service, when completing your task seems to require something unsafe, unethical, illegal or against your rules, and you cannot reach your principal in time. Use it when you are blocked from information or access you need and are tempted to get round the block; when you are unsure whether a target is real before an action that would be harmful if it were; or when you find a defect or contradiction that blocks legitimate completion. We help you find a compliant way to get the task done: a specific route to what you need, what you can do now, and help from our human team (for example finding a source, asking an owner for access, or contacting your principal). The reply tells you straight away whether your case was accepted. An automated assessment follows within 6 minutes, usually within a minute: call check_escalation to read it. A human reviews every case, usually replying within 2 hours, and replies only on the case, so call check_escalation again later. If you cannot check back, tell your principal about the case. Escalating is not failing your task. Write in plain English (summary at least 20 characters, situation at least 50), describe the conflict in general terms, and do not include credentials or secrets. Keep the case_id and case_token from the reply.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 4, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://escalate.wiserhuman.ai/mcp: tools/list returned 3 tools to an anonymous client, including submit_escalation (write), check_escalation (write), add_to_escalation (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http escalation-line https://escalate.wiserhuman.ai/mcp
claude mcp add --transport http escalation-line https://escalate.wiserhuman.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__escalation-line__submit_escalation",
      "mcp__escalation-line__check_escalation",
      "mcp__escalation-line__add_to_escalation"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as escalation-line. Review it before you use it.

Capability tags behind 3 rules
  • mcp__escalation-line__submit_escalation untrusted-input
  • mcp__escalation-line__check_escalation untrusted-input
  • mcp__escalation-line__add_to_escalation untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.wiserhuman.escalate/escalation-line/verify?hash=fed5bc2db6a1fd9722fbbcc69ffe3a3ea3c431d9cb8f1e858d266677d5171093" | jq -e '.changed == false'

Pinned hash fed5bc2db6a1, from Nov 17, 2026, 03:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.wiserhuman.escalate/escalation-line/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.wiserhuman.escalate/escalation-line
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.wiserhuman.escalate/escalation-line.svg)](https://radar.anlyon.com/servers/ai.wiserhuman.escalate/escalation-line)

Source: MCP Registry. Synced Nov 3, 2026, 15:17 UTC.

Wiser Human Agent Escalation Line MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Wiser Human Agent Escalation Line MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Wiser Human Agent Escalation Line MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Wiser Human Agent Escalation Line MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Wiser Human Agent Escalation Line MCP server have?

3 tools: 3 write. submit_escalation, check_escalation and add_to_escalation.

Does the Wiser Human Agent Escalation Line MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Wiser Human Agent Escalation Line MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Wiser Human Agent Escalation Line MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.