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


The following commit(s) were added to refs/heads/main by this push:
     new 51e67ab4eb74 Regen
51e67ab4eb74 is described below

commit 51e67ab4eb7426933d1e6229041f8bfc02e4d789
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Aug 6 21:51:37 2026 +0200

    Regen
---
 .../resources/org/apache/camel/catalog/docs/ai-tool-component.adoc      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-tool-component.adoc
 
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-tool-component.adoc
index 04ea72c081c1..78adc24c435f 100644
--- 
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/ai-tool-component.adoc
+++ 
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/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:components::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 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).
 
 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.
 

Reply via email to