feat: apply control-plane settings to MCP hooks - #144
Open
lucarlig wants to merge 1 commit into
Open
Conversation
Signed-off-by: lucarlig <luca.carlig@ibm.com>
lucarlig
added this pull request to stack #145
September 9, 2026 15:35
lucarlig
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This makes tool, prompt and resource plugins use the settings published by the control plane. Tool aliases use the same tool/team settings. Plugins receive verified caller and target details, keep their state throughout the call, and run in priority order.
The
plugin_timeoutsetting limits each plugin invocation, with a default of 30 seconds.First of two PRs; #141 adds the HTTP hooks.
Tested: 258 tests passed (13 skipped), plus formatting, lint and build checks.