MCP SERVER TERMS AND CONDITIONS

MCP Servers use or access is subject to (i) the terms and conditions herein, and (ii) the master agreement previously agreed to by your organization (“Customer”), or if none, then to the master agreement available at https://bluecatnetworks.com/license-agreements/ (as applicable, together with these terms and conditions, the “Agreement”). Capitalized terms used but not defined in these terms and conditions shall have the meaning set out in the Agreement. These terms and conditions apply to all MCP Servers made available by BlueCat with the BlueCat Offerings and supplement the Agreement. In the event of a conflict with the Agreement, these terms and conditions control solely with respect to MCP Servers.

  1. Definitions.
    • “AI Agent” means software that uses artificial intelligence or machine learning (including large language models) to discover, select, or invoke tools exposed by an MCP Server.
    • “BlueCat Offerings” means the products or services made available by BlueCat.
    • “Customer Component” means any MCP client, AI Agent, model or model-provider service, or other software or service, other than a BlueCat Offering, that is selected, supplied, or operated by or for Customer and interacts with an MCP Server.
    • “Customer Data” means data or information provided by Customer to BlueCat through access or use of the BlueCat Offerings and excludes Telemetry Data.
    • “MCP Request” means a tool call, instruction, query, or parameter submitted to an MCP Server.
    • “MCP Response” means data, content, status, or other result returned through an MCP Server.
    • “MCP Server” means any Model Context Protocol server BlueCat makes available for Customer-hosted deployment and use with a BlueCat Offering. An MCP Server is ancillary software to a BlueCat Offering.
    • “State-Changing Action” means any action that creates, modifies, acknowledges, resolves, annotates, exports, or deletes data or records, or takes any similar action in or from a BlueCat Offering.
    • “Telemetry Data” means the usage, performance, telemetry, technical, systems, and similar data associated with use or performance of the BlueCat Offerings, as described in the Telemetry Data Sheet available at https://trustcenter.bluecatnetworks.com.
  2. Enablement. BlueCat may make MCP Servers available in connection with BlueCat Offerings. Customer is responsible for configuring any administrative controls BlueCat makes available to permit or configure any connections to MCP Servers.
  3. Accuracy. An MCP Response may be incomplete, capped, truncated, or stale. Customer is solely responsible for (i) evaluating the accuracy and appropriateness of an MCP Response, and (ii) any decisions or actions taken in reliance upon the MCP Response. This Section supplements (and does not limit) the warranty disclaimers and limitations of liability in the Agreement.
  4. Use. Customer will not attempt to derive source code or otherwise use the MCP Servers or MCP Responses to develop or improve a similar or competing product or service.
  5. High-Risk Use. MCP Servers are not designed for, and Customer will not use them in connection with, high-risk or life-critical use cases. MCP Servers are not designed for uses classified as “unacceptable risk” under the EU Artificial Intelligence Act and are not intended to be deployed as “high-risk” systems under artificial intelligence laws.
  6. MCP Server License. Subject to Customer having a valid license to the applicable BlueCat Offering, BlueCat grants Customer a limited, non-exclusive, non-transferable, non-sublicensable license, for the duration of that BlueCat Offering license, to install, copy as necessary to operate, and operate an MCP Server only for internal use with that BlueCat Offering. Customer will not distribute, resell, host an MCP Server for third parties, or use an MCP Server on a standalone basis. Customer may permit its affiliates, contractors, and managed service providers to install, operate, and connect to an MCP Server only for Customer’s internal benefit on terms at least as protective of BlueCat as these terms and conditions, and remains responsible for their acts and omissions. Customer’s compliance with these terms and conditions is a condition of this license. BlueCat may terminate this license on written notice if Customer materially breaches these terms and conditions. On expiry or termination of the MCP Server license (including automatically due to expiry or termination of the license to the applicable BlueCat Offering), Customer will cease use of the MCP Server and, within thirty (30) days, uninstall and delete all copies.
  7. Nature of the MCP Server. Customer deploys and operates the MCP Server in its own environment. MCP Servers are versioned but backward-compatibility may be limited. Tools, schemas, descriptions and response formats may change, and BlueCat may modify, restrict, or remove them in future releases. MCP Servers do not follow BlueCat’s standard end-of-life and end-of-support policy and milestones. Customer is responsible for maintaining its Customer Components to tolerate MCP Server changes and for installing supported versions and security updates. Notwithstanding anything to the contrary in the Agreement, each MCP Server is provided “as is” and “as available,” with no formal support or maintenance coverage under the support program applicable to BlueCat Offerings. Any BlueCat intellectual property or similar indemnity under the Agreement does not apply to any claim to the extent arising from use of or access to an MCP Server. This Section prevails over any inconsistent provision of the Agreement as to MCP Servers.
  8. MCP Server Data; Customer Components. MCP Requests and MCP Responses are treated as Customer Data as between the parties and pass between Customer’s systems and the Customer Components. Except to the extent Customer provides them to BlueCat (including in support requests or diagnostics), BlueCat does not receive, store, or process MCP Requests or MCP Responses, and BlueCat does not engage any AI provider in connection with a Customer-hosted MCP Server. BlueCat’s data-processing, data-security, and confidentiality obligations under the Agreement, including under any data processing addendum or security exhibit, apply to Customer Data only to the extent BlueCat receives or processes it, and do not extend to Customer-hosted MCP Server deployments or to Customer Components. Customer selects and is responsible for each Customer Component, including for entering into and complying with its provider’s terms of use, acceptable use policies, and privacy and security terms. An MCP Response may include Customer Data of any category present in the applicable BlueCat Offering. Customer is responsible for determining whether its credential scope, enabled tools, and connected Customer Components are lawful for such data.
  9. Permitted Purpose; Deployment and Access Control. Customer will use MCP Servers only to monitor, analyze, and troubleshoot Customer’s own networks and environments in connection with the applicable BlueCat Offering, and only within the environments, resources, and data for which the credentials configured for the MCP Server are authorized. Customer is responsible for hosting, securing, and updating each MCP Server deployment, for determining which users, service identities, AI Agents and Customer Components may access it, and for securely issuing, storing, rotating, and revoking credentials under least privilege. For production use, Customer will deploy each MCP Server behind Customer-controlled network boundaries, use transport layer security and an authenticated mode, and not expose the endpoint to the public Internet. Customer acknowledges that an MCP Server may use shared credentials and does not itself provide per-user or role-based access control, and that the scope of the credentials Customer configures, rather than the tools exposed, determines the potential impact of any action.
  10. Human Authorization for State-Changing Actions. Before an AI Agent or other Customer Component performs a State-Changing Action, Customer will ensure the action is either authorized by a human operator or falls within a category of State-Changing Actions that Customer has pre-authorized. Customer is solely responsible for pre-authorized State-Changing Actions, including any blanket, standing, or programmatic approvals or equivalent settings. Where BlueCat provides an option to enable destructive tools, those tools will remain disabled unless Customer affirmatively determines it requires them for a defined operational purpose. Customer is responsible for any failure to implement any human review, confirmation, or approval control, or its decision to disable, override, or bypass any such control. Customer acknowledges that MCP Responses and other content available to an AI Agent or other Customer Component may include untrusted content that could induce an AI Agent or other Customer Component to take unintended actions, and Customer is responsible for client-side controls, including tool-approval settings and restricting connected servers, to mitigate that risk.
  11. Responsibility for AI Agents. Customer is responsible for the configuration and behavior of each Customer Component that interacts with an MCP Server, including its requests, retries, and loops. Losses arising from actions an AI Agent or other Customer Component performs, or that Customer implements, in reliance on an MCP Response are consequential damages for purposes of the limitation of liability in the Agreement and BlueCat shall have no responsibility for such losses. The availability, accuracy, latency, or behavior of any Customer Component is not a defect in, or failure of, a BlueCat Offering.

Last updated: August 28, 2026

📣  Now live: Explore BlueCat Horizon, our SaaS-first Intelligent NetOps platform.

Explore Horizon