Skip to content

[Access] Document tool policies, allowlists, aliases, and namespacing for MCP portals#31006

Draft
kennyj42 wants to merge 1 commit into
cloudflare:productionfrom
kennyj42:kjohnson/mcp-portal-tool-policies
Draft

[Access] Document tool policies, allowlists, aliases, and namespacing for MCP portals#31006
kennyj42 wants to merge 1 commit into
cloudflare:productionfrom
kennyj42:kjohnson/mcp-portal-tool-policies

Conversation

@kennyj42
Copy link
Copy Markdown
Collaborator

What this PR does

Adds a new 'Manage tools and prompts' section to the MCP portals page covering:

  • Turning off individual tools/prompts via dashboard
  • Allowlist pattern (default_disabled) with API example -- invert the default so only explicitly enabled tools are exposed
  • Tool aliases at server-level and portal-level, with priority resolution order
  • Tool namespacing -- explains the <serverId>_<toolName> convention

Why

Tool policies are a core feature of MCP portals but had only a single sentence of documentation ('configure the tools and prompts available through the portal'). The actual API supports:

  • Per-tool enable/disable
  • Default-disabled (allowlist) mode
  • Server-level and portal-level aliases with priority resolution
  • Automatic namespacing to prevent collisions

This is the primary governance mechanism for controlling what AI agents can do through a portal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants