ServiceNow prepares AI Passport to control AI agents’ access rights

Oct 18, 2026 | 360° IT News, AI

ServiceNow has announced AI Passport, a cryptographically signed authorisation credential designed to govern AI agents and MCP servers while workflows are running. It is scheduled to be available in the fourth quarter of 2026.[1] The image of a digital badge helps to explain the principle: an agent must be able to justify the resources it consults and the actions it takes, within a scope defined by the company.

01

An agent’s identity is not enough to define its rights

An assistant that answers a question and an agent that modifies a record do not have the same access needs. As soon as a system uses tools, it is necessary to determine what it can read, write or trigger, and in what circumstances additional approval becomes necessary.

According to ServiceNow, AI Passport makes it possible to check the authorised scope at each step of a workflow involving several agents. The system provides for delegation with progressively narrower rights, targeted revocation and graduated responses that can go as far as stopping the agent.[1]

The challenge is to make these limits effective at the moment of action. An instruction asking the agent to be careful is no substitute for a technical control capable of refusing an operation. Likewise, recording an action in a log does not, on its own, prevent it.

02

MCP connections are part of the scope to be secured

The MCP protocol connects AI applications to tools and resources. The official documentation points out that servers using authorisation must verify access tokens, in particular that the tokens are actually intended for them.[2] A technical connection to a tool is therefore not a general permission to use it.

For a company, verification must cover the whole chain: the agent, the server exposing a function and the application performing the operation. If any of these components has overly broad rights, the limits displayed in an interface may not match what is actually possible.

ServiceNow announces a collaboration with NVIDIA to enforce these controls in the infrastructure, notably with OpenShell. The Super Intelligence Control Tower is designed to keep actions traceable.[1] The actual coverage of tools and environments will need to be checked during deployment.

03

Four questions before giving an agent a badge

This editorial grid helps to translate authorisation management into concrete decisions.

Component Operational effect Control question
Scope Limit the data and tools that can be accessed. Do the rights match the assigned task?
Delegation Govern the handover of a task to another agent. Do permissions remain limited at each step?
Revocation Withdraw authorisations when the situation changes. Is the withdrawal actually enforced by connected systems?
Traceability Link an operation to its authorisation and its outcome. Can we understand who allowed the action and what it changed?

04

An authorised operation can still be wrong

Take a support agent authorised to consult tickets and draft a reply. This task does not automatically justify resetting an account or changing a network configuration. Those operations should have their own rules, with approval suited to their consequences.

Even within its scope, the agent may misinterpret a request or select the wrong record. Permission controls must therefore be complemented by testing, checking of the result and a recovery procedure. This example is a suggested framework, not a standard configuration announced for AI Passport.

05

Inventorying agents and matching costs to usage

ServiceNow is also announcing detection of unauthorised AI and AI Cost Management, expected in the fourth quarter of 2026. The aim is to link spending more closely to usage and results.[1] These functions should be distinguished from permission control itself.

06

For SMEs, start with one agent and one specific task

An SME could look at an agent already used for support or document processing. The pilot would involve identifying its access, removing unnecessary permissions and testing that an out-of-scope action is refused. It would also be necessary to check that rights are withdrawn and that the task can be taken over manually.

07

Agent security becomes an everyday administration job

This development gives Cybersecurity a central role. Professionals must apply the principle of least privilege: granting only the access needed for a task. They must understand the connections between agents, tools and applications in order to spot excessive permissions.

Their role also involves testing controls. An expected refusal must be checked in practice, as must the revocation of access or the stopping of a task. Logs must make it possible to explain actions without needlessly exposing sensitive information.

Oversight continues as usage evolves. A new connection or a change of task can alter the level of risk. The skill lies in adjusting authorisations, investigating incidents and organising the return to manual control with business teams and application owners.

08

Control will be judged at the moment of action

AI Passport highlights a key question for agentic AI: how can permissions be made verifiable and enforceable throughout a task? The answer will depend on integration with real systems. A badge will be useful if the associated controls work and if teams can understand, interrupt and correct operations.

Further reading

Four CCCLX reads to explore permissions, security and agent integration in more depth.

Systems and cloud

Azure Linux 4.0: is Microsoft preparing for life after Windows Server?

Infrastructure and system choices for cloud environments.
Open-source security

Open-source security scales up: IBM, Red Hat and Palo Alto join forces

An alliance to secure open-source software.
Coding agents

GitHub Copilot bulks up for business: coding agents come under IT control

IT teams taking control of coding agents.
Agents and cloud

AI voice agents: Oracle details a LiveKit architecture on OCI

An example of integrating agents into a cloud architecture.

Sources

  1. 01

    ServiceNow Newsroom (15 October 2026). “ServiceNow advances its operational harness for enterprise AI with AI Passport and expanded governance capabilities”. Announcement of AI Passport and the associated governance capabilities.

    View source →

  2. 02

    Model Context Protocol (accessed 16 October 2026). “Authorization”. Documentation on access token verification by MCP servers.

    View source →

Editorial check of 16 October 2026. ServiceNow plans to make AI Passport, unauthorised AI detection and AI Cost Management available in the fourth quarter of 2026. The framework examples and the SME pilot are editorial suggestions, not standard configurations or announced customer results.

360° IT News, decoding technology to understand the jobs of tomorrow.

Discover CCCLX →

Cloud, AI, defence: AWS steps up on every front

Cloud, AI, defence: AWS steps up on every front

AWS makes artificial intelligence a pillar of critical infrastructure At the AWS Summit Washington, D.C. 2026, Amazon Web Services unveiled several developments aimed at government departments, public bodies and critical sectors. The company is strengthening its...