Uh oh!
There was an error while loading. Please reload this page.
Correct custom mcpTools auth wording: anonymously invocable, no login gate - #574
Conversation
… gate Fixes#566. The "is the user logged in only" claim was wrong — custom tools register with visibleTo: () => true and the MCP route imposes no auth requirement, so anonymous sessions can list and call them. Now states that plainly and contrasts with the RBAC-filtered verb tools. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Code Review
This pull request updates the documentation in reference/mcp/tools-and-resources.md to clarify security behaviors for custom tools. Specifically, it highlights that custom tools are exposed to all MCP sessions, including anonymous and unauthenticated ones, and that developers must implement their own access control checks within the tool's method. There are no review comments, so I have no feedback to provide.
🚀 Preview DeploymentYour preview deployment is ready! 🔗 Preview URL:https://preview.harper-documentation.harperfabric.com/pr-574 This preview will update automatically when you push new commits. |
Uh oh!
There was an error while loading. Please reload this page.
🧹 Preview CleanupThe preview deployment for this PR has been removed. |
Fixes#566.
The Custom
mcpToolssection claimed "Authentication is "is the user logged in" only" — inaccurate: custom tools register withvisibleTo: () => true, the MCP route mounts with no auth requirement, and an anonymous session can list and call them (verified live by the reporter on 5.1.15, and consistent with the anonymous-session posture verified during harper#1613/#1633). The paragraph now states the anonymous exposure plainly, contrasts it with the RBAC-filtered auto verb tools, and tells authors exactly how to gate (context.usercheck in the method).Same wording had been copied into the pending mcpResources docs (#567) — corrected there in its own branch.
Generated by an LLM (Claude Fable 5).