This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel.git
commit e0211f84de85e8aa32e98f27d5780ba13cae4d54 Author: Claus Ibsen <[email protected]> AuthorDate: Thu Aug 6 21:54:06 2026 +0200 chore: Fix broken xref to mcp-server doc in ai-tool component --- components/camel-ai/camel-ai-tool/src/main/docs/ai-tool-component.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/camel-ai/camel-ai-tool/src/main/docs/ai-tool-component.adoc b/components/camel-ai/camel-ai-tool/src/main/docs/ai-tool-component.adoc index 78adc24c435f..7b305ed88951 100644 --- a/components/camel-ai/camel-ai-tool/src/main/docs/ai-tool-component.adoc +++ b/components/camel-ai/camel-ai-tool/src/main/docs/ai-tool-component.adoc @@ -199,7 +199,7 @@ The root schema must be a JSON Schema object with a top-level `properties` map. === MCP Tool Annotation Hints -When exposing `ai-tool` routes through the xref:others::mcp-server.adoc[MCP Server] component, you can declare optional behavioral hints aligned with the MCP specification (`ToolAnnotations`). MCP clients may use these hints for per-tool policy (for example auto-approving read-only tools or requiring confirmation before destructive ones). +When exposing `ai-tool` routes through the MCP Server component, you can declare optional behavioral hints aligned with the MCP specification (`ToolAnnotations`). MCP clients may use these hints for per-tool policy (for example auto-approving read-only tools or requiring confirmation before destructive ones). These hints are **advisory only** — Camel does not enforce them. MCP clients must treat them as untrusted UX metadata (per the MCP specification), not as authorization. Inaccurate hints can mislead client-side confirmation flows.
