Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
dvdksn
force-pushed
the
mcp-catalog-policy
branch
2 times, most recently
from
e018fc8 to
7a147bb
Compare
content/manuals/enterprise/security/hardened-desktop/settings-management/settings-reference.md
Show resolved
Hide resolved
| Policies are configured through Settings Management in the Admin Console | ||
| using the **MCP Policy** option. Rules can apply globally to the entire |
There was a problem hiding this comment.
Or via admin-settings.json
dvdksn
force-pushed
the
mcp-catalog-policy
branch
2 times, most recently
from
d71f2e4 to
569e0d4
Compare
dvdksn
force-pushed
the
mcp-catalog-policy
branch
from
569e0d4 to
31ce5da
Compare
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Documentation Review - No Issues Found
I reviewed all the added content in this PR, including:
- New governance.md file with MCP policy controls documentation
- Custom catalog documentation in catalog.md
- Updated index page with reorganized grid
- Governance section in toolkit.md
- Settings reference updates
The documentation is clear, accurate, and well-structured. The policy examples are comprehensive and properly explained. The custom catalog instructions provide good step-by-step guidance. No issues found that require changes.
Nice work on the comprehensive governance documentation! 🎉
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
dvdksn
force-pushed
the
mcp-catalog-policy
branch
from
31ce5da to
c7cf026
Compare
|
|
||
| Each rule can specify: | ||
|
|
||
| - `action`: Operation to control ("load", "invoke", "prompt") |
There was a problem hiding this comment.
Any guidance on what "load", "invoke", "prompt" do?
|
|
||
| Order matters. Place more specific rules before general rules to ensure | ||
| they evaluate first. For example, a rule blocking a specific tool should | ||
| come before a rule allowing all tools on a server |
There was a problem hiding this comment.
Wonder if we should add instructions on how to verification if a policy is in effect - e.g. showing it's blocked by running some CLI commands
| - `transport`: Communication method ("stdio", "sse", "streamable") | ||
| - `tools`: Array of tool names to match | ||
| - `allow`: Whether to allow (`true`) or deny (`false`) the action. Can also use `deny: true` as an alternative to `allow: false` | ||
| - `reason`: Human-readable explanation for the rule |
There was a problem hiding this comment.
Is this an exhaustive list? I have used "catalog" as one of my key to block specific catalog. Or maybe that's only applicable w/ profile?
4 participants
Preview: https://deploy-preview-24118--docsdocker.netlify.app/ai/mcp-catalog-and-toolkit/governance/