verify_handoff_token

SERVERMeridian SOURCE@meridianmcp/mcp

Low RISK CLASS

Category Read

Parameters 41 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/verify-handoff-token.md

WHAT IT DOES

What verify_handoff_token does on Meridian

AI agents call verify_handoff_token to retrieve information from Meridian 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
`token`	string	Yes	The token value from the <goal_token>…</goal_token> line in the /goal block.
`project_id`	string	—	The project_id the /goal block claims to be for.
`project_name`	string	—	Project name — an alternative to project_id; resolved to the id internally.
`presented_body`	string	—	Optional: the full pasted /goal block (token + SECURITY banner included) to check against the token's stored body_hash, if any. Closes the 2ee0000c body-integri

Parameters from the server's own tool schema.

RISK

Why verify_handoff_token is rated Low

Even though verify_handoff_token only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHandles credentials or secrets (token) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs verify_handoff_token safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For verify_handoff_token, this is the rule to start with:

verify_handoff_token Allowed

verify_handoff_token is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_handoff_token": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about verify_handoff_token

What does the verify_handoff_token tool do? +

[MAINTENANCE] Read-only: Verify a handoff provenance token (dd07ece0). When a /goal block is copy-pasted into chat rather than delivered via the trusted MCP channel (start_session pending_goal / load_handoff), a receiving session can call this tool to independently confirm the <goal_token> line was produced by a real generate_handoff call on this server — not injected or spoofed text. The token is single-use and short-lived (a few minutes); verify immediately on receipt. Returns {valid: bool, reason: str}. reason is 'ok' on success; on failure: 'not_found', 'expired', 'already_consumed', 'wrong_project', or 'body_mismatch'. efaa918a body-hash binding (closes the 2ee0000c gap): pass presented_body — the FULL pasted block, token and SECURITY banner included — and this tool strips those back out and checks the remaining text against the body hash bound at mint time. A genuine token re-attached to a DIFFERENT (edited) body now returns 'body_mismatch' instead of a false 'ok'. Omitting presented_body preserves the exact prior token-only provenance check. f46372e8: every non-'ok' result also carries a structured recovery object {signal, message, next_step, next_step_hint} telling you what to do next — next_step is 'load_handoff' (fetch the canonical stored handoff; not_found/ wrong_project/body_mismatch) or 'cross_check_live_board' (re-derive the task list from get_sprint_items across all non-done statuses; already_consumed/ expired) — so you don't have to improvise a recovery path per failure reason. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does verify_handoff_token accept? +

verify_handoff_token accepts 4 parameters: token, project_id, project_name, presented_body. Required: token. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on verify_handoff_token? +

Register the Meridian MCP server in PolicyLayer and add a rule for verify_handoff_token: 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 Meridian. Nothing to install.

What risk level is verify_handoff_token? +

verify_handoff_token is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit verify_handoff_token? +

Yes. Add a rate_limit block to the verify_handoff_token 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 verify_handoff_token completely? +

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

verify_handoff_token is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meridian, and thousands of servers like it.

This server

All 175 Meridian tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →