fix(mcp): change mcp_check_input default operation from query to execute (#106)

Follows axonflow-enterprise#1288. The check-input endpoint is called by
external orchestrators managing their own MCP execution, so defaulting to
"execute" (conservative) is semantically correct over "query" (read-only).

Author: gzak

axonflow/client.py

@@ -1189,7 +1189,7 @@ async def mcp_check_input(
         self,
         connector_type: str,
         statement: str,
-        operation: str = "query",
+        operation: str = "execute",
         parameters: dict[str, Any] | None = None,
     ) -> MCPCheckInputResponse:
         """Validate an MCP request against configured policies without executing it.
@@ -1200,7 +1200,7 @@ async def mcp_check_input(
         Args:
             connector_type: Type of MCP connector (e.g., "postgres", "snowflake").
             statement: The SQL query or command to validate.
-            operation: Operation type - "query" (default) or "execute".
+            operation: Operation type - "query" or "execute" (default).
             parameters: Optional query parameters.
 
         Returns:
@@ -6078,7 +6078,7 @@ def mcp_check_input(
         self,
         connector_type: str,
         statement: str,
-        operation: str = "query",
+        operation: str = "execute",
         parameters: dict[str, Any] | None = None,
     ) -> MCPCheckInputResponse:
         """Validate an MCP request against configured policies without executing it."""

axonflow/types.py

@@ -368,7 +368,7 @@ class MCPCheckInputRequest(BaseModel):
     connector_type: str
     statement: str
     parameters: dict[str, Any] | None = Field(default=None)
-    operation: str = Field(default="query")
+    operation: str = Field(default="execute")
 
 
 class MCPCheckInputResponse(BaseModel):