MOCK← Phase 4|policy
Policies
/
Unsanctioned MCP server in use
Mode
Confirmed on 97 of 100 endpoints
Organization Severity
high
Qpoint recommendation: medium

Findings

0open

What it tests

Detect use of an MCP server that is not sanctioned for the applicable user, team, device, or other governed scope.

Why it matters

MCP servers load tools and context into an agent without review; an unsanctioned one can read, write or exfiltrate on the user's behalf.

What fails it

An agent connects to an MCP server that is not on the sanctioned list for the subject's scope.

What happens on failure

Qpoint will block the MCP connection, and a finding records the attempt.

Mode
Until
optional: it holds until revoked
Enforce · confirmed on 97 of 100 endpointsDecides for 2 people; exceptions set the other 12.

Enforce: Qpoint will block the MCP connection.

  • Each blocked attempt is recorded as an Enforced finding.
  • Findings from before stay Observed.
  • They resolve once the block is confirmed on that person's endpoint.

Configuration

What this policy matches, set for your organisation on top of Qpoint's definition. A change is a policy change: it is recorded in History and re-evaluates the open findings it touches (D2).

Seen, not on the list

servers this policy has found, most findings first
Vanta MCP2 findings · 0 open · 2 people · last 2026-10-08
Linear MCP1 finding · 0 open · 1 person · last 2026-10-06

Sanctioned MCP servers

3 entries · patterns supported (* and ?)

ServerScopeAdded byLast matched
GitHub MCPreviewed 2026-08globalDana (security admin)2026-10-08
Atlassian MCPglobalDana (security admin)2026-10-07
Postgres MCP (read-only)analytics harnesses onlyagentSam (GRC lead)2026-10-02
you

from qdash P6 MCP Server Allow-List

Severity

new findings are generated at high · set by the organization
Level
Severity
Set by
When
Note
Qpoint recommendedmediumQpointdefinition v3
overridden by the organization
OrganizationhighDana (security admin)2026-09-30 15:10
in effect · stricter than recommended

A change reprioritises only: it never re-evaluates (D2) and never touches scope, enforcement or exceptions. Findings keep the severity they were generated with.

Exceptions

The policy is in Enforce for everyone unless an exception says otherwise. An exception sets the mode for an organization, a team or a person; the narrowest one wins, so a person's own exception beats their team's. A person in two teams whose exceptions disagree gets the stricter (D9).

Context
Sets
Reaches
Reason
Until
Set by
Team: GRC
Offover enforce
2 people
decides for 2

Approved GRC workflow with the vendor (Vanta MCP).

indefinite
Dana (security admin)
2026-09-28
Team: Engineering
ties for Alex: the stricter wins
Observeover enforce
9 people
decides for 8

Engineering is evaluating MCP servers; observe only while the sanctioned list settles.

indefinite
Dana (security admin)
2026-09-26
Team: Finance
ties for Alex: the stricter wins
Enforceover enforce
confirmed · 38 of 40 endpoints
2 people
decides for 2

Regulated data: Finance blocks unsanctioned MCP servers.

indefinite
Dana (security admin)
2026-09-24
Team: Team A
Offover enforce
1 person

Team A owns the Vanta integration.

Revoked by Dana (security admin): “Team A moved off Vanta.”

revoked
Dana (security admin)
2026-10-09

Frameworks

14 controls in 4 frameworks
Framework
Control
Shared with
Tracked
OWASP LLM Top 10
LLM03:2025Supply Chain
Partial — pin at load; sourcing is build-time
1 other policyTrackedframework →
NIST AI RMF
GOVERN 1.6Mechanisms are in place to inventory AI systems
Strong — Qpoint's live inventory is the mechanism
1 other policyUntrackedframework →
NIST AI RMF
GOVERN 6.1Policies and procedures address third-party AI risks
Partial — enforcement records prove the policy runs; writing it is yours
3 other policiesUntrackedframework →
NIST AI RMF
GOVERN 6.2Contingency processes handle failures in high-risk third-party data or AI systems
Partial — block a failing provider or server; the contingency plan is yours
1 other policyUntrackedframework →
NIST AI RMF
MANAGE 2.4Mechanisms supersede, disengage or deactivate AI systems that act outside intended use
Strong — block a provider, model or MCP server, with timestamped enforcement
2 other policiesUntrackedframework →
NIST AI RMF
MANAGE 3.1Third-party AI risks are monitored and controls applied and documented
Strong — third-party AI use is what Qpoint sees
3 other policiesUntrackedframework →
NIST AI RMF
MAP 4.1Risks of AI components, including third-party data and software, are mapped
Partial — which data reaches which provider and tool feeds the map
2 other policiesUntrackedframework →
NIST AI RMF
MAP 4.2Internal risk controls for AI components, including third-party, are documented
Addressable — the Policy Config is the documented control set
2 other policiesUntrackedframework →
NIST AI RMF
MEASURE 3.1Existing, unanticipated and emergent AI risks are tracked
Strong — first-seen tools and models, shadow AI
3 other policiesUntrackedframework →
OWASP Agentic Top 10
ASI04Agentic Supply Chain Vulnerabilities
Addressable — inventory, pinning, kill switch
2 other policiesUntrackedframework →
OWASP Agentic Top 10
ASI10Rogue Agents
Partial — expected vs observed, and the kill switch
2 other policiesUntrackedframework →
SOC 2
CC3.2Identify and analyze risks
Partial — the inventory feeds the risk assessment
1 other policyUntrackedframework →
SOC 2
CC6.8Prevent or detect unauthorized or malicious software
Strong — for unapproved agents, harnesses and MCP servers
2 other policiesUntrackedframework →
SOC 2
CC7.1Detect configuration changes and new vulnerabilities
Partial — new tools and versions, first seen
1 other policyUntrackedframework →

Rows for an untracked framework are dimmed. Tracking one changes no policy and re-evaluates nothing.

Findings

0 open · 3 resolvedall in Findings →

No open findings for this policy.

History

5 changes

Every auditable change to this policy's configuration. Finding lifecycles point at these rows as their cause.

When
By
Change
Detail
Id
2026-10-14 08:00Dana (security admin)exception revokeException E-A revoked: Team A moved off VantaCH-5
2026-10-09 11:05qdashenforcement confirmEnforcement confirmed on 97 of 100 devices (Vanta MCP blocked on mac-b1 at 11:05)CH-3
2026-10-09 09:40Dana (security admin)mode setMode set to Enforce: block the MCP connectionCH-2
2026-10-09 09:15Dana (security admin)exception addException: Off for Team A — Team A owns the Vanta integrationCH-1
2026-09-30 15:10Dana (security admin)severity overrideConfigured high (recommended medium)—