d365fo-client

The MCP server incorporates authentication mechanisms (API Key or Azure AD) which are crucial for its security. The core client handles D365 F&O authentication securely (Azure Default Credentials or client_id/secret/tenant_id via environment or Key Vault). However, the `d365fo_execute_sql` tool within the MCP server exposes direct SQL querying capabilities to the underlying SQLite metadata cache. While there's a `_validate_query_safety` mechanism mentioned, exposing raw SQL via an API, even to a local cache, is inherently a high-risk surface area if not perfectly implemented and contained. Deploying the MCP server over HTTP/SSE with inadequate network access controls or weak authentication could lead to unauthorized data access or manipulation of the metadata cache. Ensure strong authentication is enabled and only trusted entities can access the MCP server's endpoints.