Documentation
¶
Overview ¶
Package capguard keeps the methods this server answers in step with the capabilities it declares.
The go-sdk wires a handler for every method in the protocol, whether or not the server opted into the feature behind it. Two mismatches result here: logging/setLevel succeeds with an empty result although the handshake never declares the logging capability (this server logs to stderr and never emits notifications/message to a session), and on the minimal capability surface prompts/list answers a successful empty page while the handshake declares no prompts capability. Both pairs have no honest reading — a success invites the client to keep asking for a feature the handshake already said does not exist, while -32601 says so once and for all.
The pattern (and the package name) is shared with the sibling libgen-mcp's capguard, which draws the same line for its resource methods.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func Undeclared ¶
func Undeclared(methods ...string) mcp.Middleware
Undeclared returns receiving middleware that answers the given methods with JSON-RPC -32601, the code JSON-RPC 2.0 reserves for a method that "does not exist / is not available" and the one the SDK itself returns for the optional handlers it can gate (an unwired resources/subscribe, completion/complete without a CompletionHandler). Every other method passes through untouched.
Gate a method here only while its capability is withheld from the handshake: gating a declared capability's method would create the same contradiction this middleware removes, pointing the other way.
Types ¶
This section is empty.
Source Files