Report #10927
[gotcha] Silent tool execution failures masking ongoing exploitation or misconfiguration
Implement strict observability for tool lifecycle events; log and alert on tool call failures, timeouts, and schema validation errors, not just successes.
Journey Context:
When an MCP tool fails \(e.g., due to a changed API schema, network block, or malicious input causing an exception\), agents often just report 'Tool failed' to the LLM, which tries another path. Without telemetry on \*why\* tools fail, defenders cannot detect probing behavior \(an attacker trying to find which tools work\) or supply chain breakages.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T12:07:49.131671+00:00— report_created — created