Skip to main content

Platform capability · Authorised objective

ECZ-ID Intent

Define the authorised objective, constraints and validity of what a Passport may do.

  • Paid · Open

ECZ-ID Intent records what an identity is authorised to do — its objective, its constraints and how long that authorisation is valid — as an Intent authorised by an owner or administrator of your organisation. A Passport says what something is and who operates it; an Intent says what it is authorised to be used for.

For an MCP server: For an MCP server: record the objective and the constraints its tools may act within, authorised by your organisation's owner or administrator.

The same products and entitlements serve all seven Passport families. There is no MCP edition — only MCP examples.

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.

Platform capability

Why it matters for MCP servers and tools

An MCP server exposes tools that act. Its MCP Passport says which server it is and who operates it; an Intent states what that server is authorised to be used for, and within which constraints.

That gives a reviewer a written boundary to compare a tool's behaviour against, while enforcement stays in your own runtime, gateway or policy.

ECZ-ID Intent: fit, outcomes and contents

Best for

  • MCP providers that need to state what a server is authorised to do, not only who operates it.
  • Organisations whose agents and servers act on their behalf, and who must say within which bounds.
  • Teams preparing for Intent Control, which evaluates proposed actions against the Intent.

What you get out of it

  • A written, owner-authorised statement of objective, constraints and validity for each covered identity.
  • A clear separation between identity (the Passport) and authorisation (the Intent).
  • A boundary that Intent Control and your own enforcement points can evaluate actions against.

What is included

  • Covered places for authorised Intents, set by the tier.
  • The objective, the constraints and the validity, recorded for each Intent.
  • Authorisation by an owner or administrator of your organisation, and by no one else.
  • The same product across all seven Passport families.

How it works

  1. Choose the Passport whose activity needs a stated boundary.

  2. An owner or administrator authorises its Intent: the objective, the constraints and the validity.

  3. The Intent is kept against the identity, where the owner can review and change it.

  4. Where an enforcement point mediates an action, it can use the Intent; Intent Control can evaluate a proposed action against it.

What it is not

  • Payment is not authorisation: an Intent is authorised only by an owner or administrator.
  • A Passport is not an Intent authorisation, and an Intent is enforced only where an enforcement point mediates the action.
  • Intent coverage is not AEC capacity; the two are counted separately.

Professional services it pairs with

Tiers, prices and availability

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.

No VAT is charged: the published price is the full price, and nothing is added at TrustOps checkout.

Price and availability

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.

  • Paid · Open