BobSong-dev opened a new issue, #7959: URL: https://github.com/apache/shenyu/issues/7959
## Background P2-16 in the mentor-approved OSPP plan; parent #7949. MCP prompts provide client-facing templates and need their own list/get authorization and bounded aggregation contract. ## Existing capabilities and reuse Reuse Agent Gateway tools catalog snapshots, remote connection/credential lifecycle, trusted identity and list/execution authorization patterns. Existing tools-only behavior remains compatible. Existing resources PR #7669 is separate prior work, not a prerequisite or a replacement for prompts. ## Implementation scope - Add local/remote prompts/list and prompts/get with deterministic naming/conflict handling, correct routing and argument validation. Document naming before implementation; do not silently change existing tools names. - Enforce consistent list visibility and get authorization with deny precedence and tenant isolation; use trusted capability grants rather than treating tool access as prompt access. - Implement capability advertisement, pagination and directory-change handling only as required by the selected supported protocol; preserve coherent snapshots under refresh/removal. - Bound discovery/result sizes, concurrency and cancellation; reuse target-bound credentials and P1-08 recovery rather than new transport infrastructure. ## Non-goals Automatic prompt-injection protection, implicit authorization to execute tools described by a prompt, full MCP protocol completion, resources subscriptions/templates, or unconditional SDK migration. ## Acceptance criteria - [ ] A documented real MCP client can list/get both local and remote prompts through the gateway with deterministic routing. - [ ] Unauthorized prompts are neither listed nor retrievable; removed/revoked definitions cannot reappear through stale snapshots. - [ ] Argument errors, pagination, naming conflicts, unsupported capabilities, bounded responses, timeout and cancellation have explicit protocol-consistent behavior. - [ ] Existing tools and legacy MCP Server paths remain compatible and credentials/content do not leak into logs. ## Tests Parser/handler/catalog/provider tests; actual client -> gateway -> MCP server list/get fixture; multiple servers with name collisions, pagination and changing definitions; tenant/grant isolation and revoke/refresh races; error/cancel/oversize and tools coexistence regressions. ## Dependencies P0-01/P0-02, P1-07 and P1-08. P2-15 SDK migration becomes a prerequisite only if this selected protocol/client path demonstrates a genuine compatibility or maintenance trigger; otherwise reuse the current stack. P3-17 is not a prerequisite. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
