Gineadh an t-aistriúchán seo le meaisín agus tá sé ag feitheamh ar athbhreithniú.Athraigh go Béarla

MCP SERVER

Read-only MCP over the tenant's own risk telemetry

An approved external AI client can query scoped tenant data with a token your team issues. Calls are audited, and tokens can be revoked.

WHAT IT DOES

Structured context for approved AI workflows

MCP makes approved reads machine-consumable. Action and authorization stay in your own systems.

Your MCP client

Bearer token

  • Scope A
  • Scope B
  • Scope C: not in this token

The narrowest useful scope for each integration.

The tenant the token was issued to

Read-only tools

  • Policies
  • Rules
  • Alerts
  • Risk distribution

Every tool is a read. Calls are recorded, including denied calls.

Another tenant

Out of reach: the token is tenant-bound.

  • Read-only: no configuration changes, no action on traffic
  • Responses are data to interpret, not instructions
  • Can be out of date after configuration or traffic changes
Scoped and tenant-bound: a token reaches read-only tools for its own tenant, and nothing beyondIllustration with example labels, not customer data.
  • Read-only tools

    Supported tools read policies, rules, alerts and risk distribution for the tenant. The tools for tenant analytics are read-only.

  • Scoped, tenant-bound tokens

    A token can read the surfaces its scopes allow, for the tenant it was issued to, and nothing beyond that. Requests are subject to the tenant's provisioned rate limits.

  • Audited calls

    Calls are recorded, including denied calls, so operators can review which integration requested what and when.

  • Controlled token lifecycle

    An authorized operator creates, rotates and revokes tokens after a fresh multi-factor check. Tokens expire.

HOW IT WORKS

From approval to a reviewed answer

The connection is set up with Noxtica. It is not an open endpoint.

  1. Console

    Issue a scoped token

    An authorized operator creates a token with the narrowest useful read scopes.

  2. Your MCP client

    Present the token

    Bearer token

    An MCP-compatible client, set up with the details from your tenant provisioning.

  3. Noxtica

    Read-only tools

    A supported read

    Reads the tenant's own risk telemetry within the token's scopes. Calls are audited, including denied calls.

  4. Your team

    Human review or your automation

    Data, not instructions

    The client interprets the response. Decisions and actions stay in your own systems.

How a scoped token turns into a read-only answer your team reviews
  1. Confirm access for the tenant

    Confirm eligibility with Noxtica. MCP access follows the tenant's plan tier and is subject to operator gates and limits.

  2. Issue a scoped token

    An authorized operator creates a token with the narrowest useful read scopes.

  3. Connect a client and review

    Configure an MCP-compatible client with the provisioned details and request a read. Route the result to human review or your own automation.

WHERE IT FITS

Where MCP access helps

MCP gives a workflow structured context. Decisions and actions stay with your team.

  • Investigation briefs

    Add recent alerts to a brief that a person reviews.

  • Policy summaries

    Summarize a tenant's current policies or rules before a review.

  • Operations reporting

    Describe risk distribution for a periodic operational report.

HOW TEAMS CONNECT IT

How a team connects it

Connection details are provided during tenant provisioning.

  1. Use an MCP-compatible client that can send a bearer token.
  2. Take the connection details and supported tools from your tenant provisioning. Do not infer endpoints or scopes from examples.
  3. Keep the token out of browser code and prompts, and give each integration the narrowest useful scope.

LIMITS

Boundaries and responsibilities

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, and open or public connections are not offered.
  • The tools for tenant analytics are read-only. They do not change Noxtica configuration or act on traffic. Actions stay in customer-owned systems.
  • Responses are data for the client to interpret, not instructions. They can be out of date after configuration or traffic changes.
  • 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.

FAQ

Questions about the MCP server

Can an AI client change my Noxtica settings?

The tools for tenant analytics are read-only. They do not change configuration or act on traffic.

Can anyone connect an AI client?

No. Access follows the tenant's plan tier and operator gates, and every connection needs a token issued by an authorized operator.

How is MCP different from the AI assistant?

The assistant runs inside the console for a signed-in operator. MCP lets an approved external client read scoped data with a token. They are provisioned separately.

MCP SERVER

Ask about MCP access

Contact the Noxtica team to confirm eligibility and enablement for your tenant.