feat: plan v1#9
Merged
Merged
Conversation
imbenrabi
marked this pull request as ready for review
October 9, 2025 07:08
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
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.
Permission-Based Toolset Access Control
Overview
This PR introduces a new permission system for Toolception that enables per-client access control to toolsets. Server operators can now restrict which toolsets each client can access, supporting multi-tenant deployments and security-sensitive environments.
Key Features
Per-Client Toolset Permissions
Each client receives only the toolsets they're authorized to access. Permissions are resolved at connection time and enforced throughout the session lifecycle.
Two Permission Sources
Header-Based Permissions
Clients send their allowed toolsets via HTTP headers
Useful for proxy-based authorization or API gateway integration
Default header: mcp-toolset-permissions (configurable)
Config-Based Permissions
Server-side permission resolution using static maps or custom resolver functions
Supports fallback chains: resolver → static map → defaults
Ideal for centralized permission management
API