Stéphane Tailland
934adf0cfc
Adds the restocker KongConsumerGroup and patch-product to the tools policy, allow: [admin, product_manager, restocker]. classic-models-api backs this the same way — restocker may PATCH a product and nothing else. Regenerated with generate-mcp-tools.py. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
26 lines
1.0 KiB
YAML
26 lines
1.0 KiB
YAML
# Which operations of openapi.yaml become MCP tools, and who may call each.
|
|
#
|
|
# This file is the allow-list as well as the ACL: an operation that is not
|
|
# named here does not become a tool. Kong's generator exposes every operation
|
|
# it finds and can express no authorization at all from a bearer-token spec —
|
|
# see k8s-platform/MCP-TOOL-GENERATION.md, limits 1 and 5.
|
|
#
|
|
# `allow` lists consumer groups, which come from realm_access.roles in the end
|
|
# user's own token. Kong applies them at tools/list, so a caller never sees a
|
|
# tool it may not call.
|
|
|
|
mcp_name: catalog-mcp
|
|
|
|
tools:
|
|
list-products:
|
|
allow: [admin, read_only, product_manager, customer, support]
|
|
get-product:
|
|
allow: [admin, read_only, product_manager, customer, support]
|
|
create-product:
|
|
allow: [admin, product_manager]
|
|
patch-product:
|
|
# restocker: the fulfilment identity moving stock on delivery. The Django
|
|
# side backs this the same way — CatalogPermission accepts restocker on
|
|
# PATCH only, never create/replace/delete.
|
|
allow: [admin, product_manager, restocker]
|