TL;DR: Task IDs can act like bearer-like credentials in MCP Tasks when requests are not bound to the authenticated principal, according to Mindgard. That leaves task results, notifications, and cancellation rights exposed unless every request is checked against identity.
Editorial analysis by NHI Mgmt Group, based on content published by Mindgard: “Zero Auth != Zero Trust: The MUST that Never Made it into MCP's New Tasks Extension”.
Key questions
Q: Why does missing authorization in a protocol spec matter more than a single implementation bug?
A: A single bug affects one deployment, but a missing requirement in the spec can be reproduced by every conformant implementation.
Q: How can teams tell whether a task system is actually enforcing ownership?
A: Look for a principal-bound decision on every task-related request, not just a capability check or a hard-to-guess identifier.
Q: What breaks when task IDs are treated as the only access control?
A: Task IDs stop being harmless references and become bearer-like credentials.
Practitioner guidance
- Authorize every task request Check each tasks/get, subscriptions/listen, and input-response action against the authenticated principal before returning any state or side effect.
- Bind server state to a derived user identifier Store task ownership against a server-derived identifier instead of a caller-supplied token so that reassignment and impersonation are not possible.
- Make unauthorized and missing look identical Return the same error for not-yours and does-not-exist cases, and apply rate limits so task existence cannot be probed as an oracle.
Bottom line: The core issue is not guessing resistance but missing authorization, which allows task identifiers to function like bearer credentials.
Glossary terms: Capability URL, Principal Binding, Existence oracle, Bearer-like credential
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Task IDs have become a capability boundary, not a lookup key: In MCP Tasks, the identifier itself can gate access to results and side effects, which means the governance question shifts from where a task lives to who can exercise it. That is a material change for identity design because object possession can now behave like authority. Practitioners should treat task handles as security-bearing artifacts, not implementation details.
A few things that frame the scale:
- 90% of IT leaders say properly managing NHIs is essential for a successful zero-trust implementation, according to the Ultimate Guide to NHIs.
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: Should task lifetime be tied to the credential that created it?
A: Yes, because task state that outlives the issuing credential becomes harder to govern and revoke. If revocation does not end task access, the system can retain authority beyond the session or principal that created it, which creates an avoidable persistence window.
👉 Read our full editorial: MCP Tasks exposes a bearer-token gap in task authorization