Conversation
Co-Authored-By: Martin Vasko <Matovidlo2@gmail.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
There was a problem hiding this comment.
Pull request overview
This PR adds comprehensive documentation for the new Tool Authorization and Access Control feature in the Keboola MCP Server, enabling granular control over which tools are available to clients via HTTP headers.
Changes:
- Added "Tool Authorization and Access Control" section documenting three HTTP headers (
X-Allowed-Tools,X-Disallowed-Tools,X-Read-Only-Mode) for controlling tool access - Documented filter application order and behavior when multiple headers are combined
- Listed all 15 read-only tools categorized by function (Components, Flows, Storage, SQL, Data Apps, Jobs, Search, Project, Documentation)
- Provided practical use case examples for AI agent restrictions, compliance scenarios, and combined restrictions
- Fixed minor formatting issue at end of file (removed extra pipe character)
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-Authored-By: Martin Vasko <Matovidlo2@gmail.com>
Jira issue(s): N/A (documentation for mcp-server PR #350)
Link to Devin run: https://app.devin.ai/sessions/4ccc6d6f64aa49a6823bf2e09c8a5091
Requested by: Martin Vasko (@Matovidlo)
Changes:
X-Allowed-Tools,X-Disallowed-Tools,X-Read-Only-ModeUpdates since last revision:
This documentation corresponds to the new
ToolAuthorizationMiddlewarefeature being added in keboola/mcp-server#350.Human Review Checklist
READ_ONLY_TOOLSfrozenset in mcp-server PR add length to example #350/ai/mcp-server/resolves correctly in the deployed documentation