MCP Server - Usage Policy

Version 1.0 – effective 19 November 2026

What the MCP Server is

The MCP Server is part of your 3decision licence. It implements the Model Context Protocol so that an AI assistant you choose (for example, Claude or Microsoft Copilot) can call 3decision functions on behalf of your users. One MCP Server instance is deployed per 3decision environment and serves only the users of that environment. For 3decision deployments hosted in your own infrastructure, the MCP Server is deployed in the same environment.

Access and permissions

Each connection uses the personal 3decision API key of a named user. The AI assistant can only see and do what that user can already see and do in 3decision; the MCP Server grants no additional rights. Please keep API keys confidential, do not share them between users, and revoke them when a user no longer needs access. The API key is stored in the configuration of your AI assistant, so protect it there as you would a password.

Your AI assistant

You choose, configure, and operate your AI assistant and its underlying model. Data that your assistant retrieves through the MCP Server is sent by you to your AI provider, under your terms with that provider. Discngine itself does not send your data to any AI model. Please check that this use fits your internal policies, including any rules on AI providers training on your data.

Read and write access

By default, the MCP Server is “read-only”: your AI assistant can search and read 3decision data, but cannot create, modify or delete anything. When requesting MCP access, you may choose “read and write” access instead. Discngine then enables a limited set of write functions for your environment. Your AI assistant can list the functions available to it at any time.

This setting applies to your entire 3decision environment and cannot be configured per user. Write functions are identified as such, so AI assistants that support this can ask users to confirm each change; Discngine does not control how your assistant applies this.

Limits and resources

The MCP Server uses the same rate limits and computing resources as the 3decision API, including the number of parallel jobs. If you need more, contact us: additional resources are quoted and agreed with you in writing before they apply. We do not bill based on usage.

Discngine's commitments

  • We do not use your data or the results you generate to train or fine-tune any AI model.

  • We keep technical usage logs of the MCP Server for up to 12 months, for security and support only. They contain no user identity, no IP addresses, and no customer data. Per-user traceability stays in the 3decision audit logs. Where 3decision runs in your infrastructure, your own log retention applies.

  • The MCP Server is part of the 3decision service and is covered by the same availability and support commitments.

Using your AI assistant with 3decision results

Your agreement may restrict the use of machine learning on 3decision results. Using your AI assistant through the MCP Server, as described in this policy, is permitted under that restriction. Systematic bulk extraction, circumventing the usage limits, or training a model to replicate 3decision is not permitted.

Important to know

  • AI assistants can produce answers that are inaccurate or incomplete, even when the underlying 3decision data is correct. Have a qualified person review AI output before relying on it for scientific or business decisions.

  • The MCP Server is designed with the safeguards recommended for AI integrations. It is read-only by default; it acts only within each user’s existing 3decision permissions, and it passes content from 3decision to the assistant as data, not as instructions. These measures protect against “prompt injection,” a risk common to all AI assistants, in which text within the data an assistant reads attempts to steer its behaviour. How the assistant itself interprets content is handled by your AI provider.

  • Files generated through the MCP Server (for example, structure or data exports) are private to the session and can only be accessed through the download link created for them. Anyone who has that link can download the file. Files are kept for up to 24 hours, and links remain valid for up to 1 hour; both durations can be adjusted for your environment on request.

  • 3decision and its MCP Server are designed for structure-based drug discovery research. They are not intended for clinical, diagnostic, or patient-related use.

Changes to this policy

The MCP Server will evolve with AI assistants and the protocol. We will publish updated versions of this policy and inform your main contacts of material changes. This policy does not amend your agreement with Discngine. If anything here conflicts with your agreement, your agreement prevails, except that section 7 constitutes Discngine's written consent under the machine-learning restriction in your agreement.

Requesting, changing or stopping MCP access

To request access, use the Request MCP access button in 3decision or email 3decision-support@discngine.com. Discngine confirms each request with your organization's main contacts before enabling the MCP Server. To switch between read-only and read-write, or to switch the MCP Server off, email 3decision-support@discngine.com.

Contact

For questions about the MCP Server: 3decision-support@discngine.com.