fix: guard_sync wraps TimeoutError, cancels pending future on timeout

capiscio_mcp/guard.py

@@ -688,7 +688,19 @@ async def run_eval():
                 # We're in an async context, use run_coroutine_threadsafe
                 import concurrent.futures
                 future = asyncio.run_coroutine_threadsafe(run_eval(), loop)
-                result = future.result(timeout=30.0)
+                _GUARD_SYNC_TIMEOUT = 30.0
+                try:
+                    result = future.result(timeout=_GUARD_SYNC_TIMEOUT)
+                except (TimeoutError, concurrent.futures.TimeoutError):
+                    future.cancel()
+                    raise GuardError(
+                        reason=DenyReason.INTERNAL_ERROR,
+                        detail=(
+                            f"Guard evaluation timed out after {_GUARD_SYNC_TIMEOUT}s. "
+                            "This usually means the guard is being called outside of "
+                            "an MCP request context or the gRPC core server is not responding."
+                        ),
+                    )
             else:
                 # No event loop, create one
                 result = asyncio.run(run_eval())

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "capiscio-mcp"
-version = "2.7.1"
+version = "2.7.2"
 description = "Trust badges for MCP tool calls - RFC-006 & RFC-007 implementation"
 readme = "README.md"
 requires-python = ">=3.10"