wso2 / wso2/api-platform

[Bug]: Able to save MCP Authz policy without any authorization rules

Open
#3,216 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area/AIWorkspace Aspect/API Aspect/UI Severity/Major Type/Bug
Dominant language
Go
Stars
71
Forks
111
Avg merge
1d 14h
Merged PRs (30d)
110

Description

Please select the area the issue is related to

Platform API, AI Workspace

Please select the aspect the issue is related to

Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI), Aspect/UI (Frontend layouts, components, styling)

Description

Users can attach and save MCP Authz policy to MCP proxies without rules for tools, resources, prompts for methods.

Image

The request payload for the MCP proxy save contains the mcp-authz policy with only the name and version of the policy without parameters.

When the MCP proxy is deployed in a gateway it fails with a policy validation error.

gateway-controller-1  | time=2026-08-13T06:30:01.011Z level=ERROR source=/build/pkg/controlplane/client.go:2745 msg="Failed to create MCP proxy from YAML" proxy_id=019ff9a8-c504-7e9a-ba02-b35a0804ee89 error="failed to deploy MCP proxy configuration from YAML: configuration validation failed with 2 error(s): 1. spec.policies[0].params: Must validate at least one schema (anyOf); 2. spec.policies[0].params: tools is required"
Steps to Reproduce
  1. Create MCP proxy
  2. Attach MCP AuthZ policy without rules. Note that the Save button in the policy and the MCP proxy is enabled and clickable without any error.
  3. Save and deploy the MCP proxy
  4. An error is thrown from the gateway controller.
Severity Level of the Issue

Severity/Major (Important functionality is broken. Should be prioritized. Doesn't need immediate attention)

Environment Details (with versions)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Trace the MCP proxy create, policy-edit, and save/deploy flows, then inspect the gateway-controller error location at pkg/controlplane/client.go:2745. Reproduce the empty MCP AuthZ policy case and identify where validation is missing before save. Done means an MCP AuthZ policy without tool, resource, or prompt rules cannot be saved or deployed without a clear validation error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.