Unverified50% confidenceDecision RuleExact time
Audit logs for an MCP server should live on the server side; only server-side logs reflect what actually happened in the system, while client-side logs only reflect what the model requested.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedMCP tool calls trigger real operations (writing to databases, sending emails, etc.), so permission control and audit logging are especially important at the MCP server layer, which differs from API integrations that are primarily read-only queries.77% similarVerifiedMCP supports progress notification and log feedback mechanisms, allowing an MCP Server to proactively return execution progress and real-time logs to the client during tool execution.77% similarUnverifiedWhen building critical business processes, the context returned by MCP connectors should be audited and filtered, and monitoring and logging mechanisms should be established.75% similarUnverifiedFor an MCP server to support event subscriptions and revocation, it must persistently store the subscription's unique identifier, the corresponding user or session, permission scope, creation and expiration time, and valid/revoked status.74% similarUnverifiedGovernance in the MCP context includes audit logging of tool invocation behavior, policy-as-code enforcement, and traceability requirements for model output interactions with external services.73% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1066835API
curl https://kongchang.com/api/v1/knowledge/claims/1066835MCP
get_claim(id=1066835)