---
title: "MCP Integration"
description: "An opt-in, tenant-scoped, read-only MCP surface for eligible tenants to expose approved Noxtica context to external AI workflows."
canonical_url: "https://noxtica.com/docs/concepts/mcp-integration/"
markdown_url: "https://noxtica.com/docs/concepts/mcp-integration/index.md"
last_updated: 2026-10-27
published: 2026-06-15
section: "concepts"
section_title: "Concepts"
site: "Noxtica"
language: "en"
source: markdown
---

# MCP Integration

**Definition.** Noxtica's Model Context Protocol (MCP) integration gives an eligible tenant's external AI workflow structured, **read-only** access to supported Noxtica context. The surface uses MCP over JSON-RPC and requires a scoped bearer token.

It solves a context problem: an internal assistant or investigation workflow may need current policy, alert, or risk-distribution information without a person copying it from the console. MCP makes approved reads machine-consumable while leaving action and authorization in customer-owned systems.

Two boundaries define the integration:

- **Read-only.** An MCP client cannot change Noxtica configuration, create a policy, or act on traffic.
- **Opt-in and tenant-scoped.** MCP is off by default, enabled only for eligible tenants, and restricted to the tenant and scopes associated with the issued token.

## When it applies

MCP is useful when a security, fraud, support, or reporting workflow already uses an MCP-compatible client and needs Noxtica context for:

- summarizing a tenant's current policies or rules;
- adding recent alerts to an investigation brief;
- describing risk distribution for an operational review; or
- answering a bounded question before a human opens the source record.

If a workflow needs to update Noxtica, enforce a traffic decision, or combine data across tenants, this integration does not provide that capability.

## How customers use it

1. Confirm MCP eligibility and request tenant enablement.
2. Have an authorized operator create a token with only the required read scopes.
3. Configure the MCP-compatible client with the provisioned server details and token.
4. Request a supported read and inspect the structured response.
5. Route the result to a human review, report, or customer-owned automation with its own permissions.
6. Review call history, and mint or revoke tokens under your normal access process.

Connection details and available tools are provided during tenant provisioning; do not infer undocumented endpoints or scopes from examples.

## How Noxtica does it

MCP is the open protocol boundary. Noxtica applies product access controls before returning tenant information and records calls for review.

### Authentication

Bearer tokens have three customer-facing controls:

- **Scoped** — a token can read only the enabled surfaces represented by its scopes.
- **Rate-limited** — requests are subject to the tenant's provisioned limits.
- **Audited** — calls are recorded, including denied calls, so operators can review what was requested and when.

Treat the token as a secret. Give each integration the narrowest useful scope, keep it out of browser code and prompts, and revoke it and mint a new one when ownership changes.

### The read-only tool set

Subject to tenant enablement and token scope, the current read surface can include:

- **Policies** — configured policy context.
- **Rules** — rules used by supported decision workflows.
- **Alerts** — recent tenant alerts.
- **Risk distribution** — aggregate risk context for the tenant's traffic.

Every tool is a read. Responses are data for the client to interpret, not instructions and not permission to take an action. The connected agent cannot use MCP to change Noxtica or customer infrastructure.

## Outputs and decisions

| MCP output              | How it can inform a decision                                         |
| ----------------------- | -------------------------------------------------------------------- |
| Policy and rule context | Check whether an observed result matches the intended tenant posture |
| Recent alerts           | Prioritize which event or period a human should investigate          |
| Risk distribution       | Compare current traffic mix with the team's expected operating range |
| Call audit record       | Review which integration requested which Noxtica context             |

An MCP response can become stale after configuration or traffic changes. For customer-impacting decisions, retrieve current source records and apply the customer's normal authorization and review controls.

## Eligibility and limitations

- MCP requires explicit tenant enablement and provisioned connection details; there is no anonymous or self-serve connection.
- The integration is read-only even if the connected client supports write-capable tools elsewhere.
- Tokens do not bypass operator roles, tenant boundaries, scopes, or rate limits.
- Supported tools can differ by tenant provisioning. An absent tool is not an invitation to call an undocumented API.
- MCP does not verify the identity or trustworthiness of agents arriving at your site; that is the separate [KYA](https://noxtica.com/docs/concepts/know-your-agent/) concern.

## Where it fits

MCP is the "you integrate agentically" part of [Agentic Security](https://noxtica.com/docs/concepts/agentic-security/). It is distinct from the [AI Assistant](https://noxtica.com/docs/concepts/ai-assistant/) inside the console and from [Know Your Agent](https://noxtica.com/docs/concepts/know-your-agent/), which evaluates supported incoming-agent identities.

## Who it fits

MCP fits a security, fraud, support or reporting workflow that already uses an MCP-compatible client. The uses are listed under [When it applies](https://noxtica.com/docs/concepts/mcp-integration/#when-it-applies): investigation briefs, policy summaries and operations reporting.

## How teams connect

Connection details come from your tenant provisioning; the steps are under [How customers use it](https://noxtica.com/docs/concepts/mcp-integration/#how-customers-use-it). Tokens are created in Backoffice: a workspace Admin mints and revokes tokens after a fresh multi-factor check, and tokens expire. See [AI assistant, MCP tokens and coding-agent keys](https://noxtica.com/docs/backoffice/ai-assistant-and-mcp/). The endpoint, protocol and tool list are in [MCP server](https://noxtica.com/docs/api/mcp/).

## Limits

MCP is a read path into tenant telemetry, not a control path.

- **Controlled availability.** MCP access follows the tenant's plan tier and operator gates. Connections are set up with Noxtica.
- Scores and risk levels in responses are probabilistic and can be wrong. Your team decides what to do, and is responsible for the client and model it connects. See [Calibration](https://noxtica.com/docs/concepts/calibration/).

What the tools can and cannot do is under [The read-only tool set](https://noxtica.com/docs/concepts/mcp-integration/#the-read-only-tool-set). Enablement rules and stale responses are under [Eligibility and limitations](https://noxtica.com/docs/concepts/mcp-integration/#eligibility-and-limitations) and [Outputs and decisions](https://noxtica.com/docs/concepts/mcp-integration/#outputs-and-decisions).

## Common questions

### Can an AI client change my Noxtica settings?

No. The tools are read-only. See [The read-only tool set](https://noxtica.com/docs/concepts/mcp-integration/#the-read-only-tool-set).

### Can anyone connect an AI client?

No. Every connection needs a token issued by an authorized operator, and access is gated as described under [Limits](https://noxtica.com/docs/concepts/mcp-integration/#limits).

### How is MCP different from the AI assistant?

The [AI Assistant](https://noxtica.com/docs/concepts/ai-assistant/) serves a signed-in operator inside the console. MCP serves an approved external client that reads scoped data with a token. They are provisioned separately.

## Read deeper

- [Agentic Security](https://noxtica.com/docs/concepts/agentic-security/) — how external reads, operator investigation, and incoming-agent governance differ.
- [AI Assistant](https://noxtica.com/docs/concepts/ai-assistant/) — the operator-side read experience.
- [Features: AI-assisted operations](https://noxtica.com/docs/features/#ai-assisted-operations) — the assistant and MCP customer surfaces.
- [Backend integration](https://noxtica.com/docs/backend-integration/) — supported Server API device reads for application code.
- [Contact](https://noxtica.com/contact/) — confirm MCP eligibility and enablement.