Skip to main content

Platform capability · Action evaluation

ECZ-ID Intent Control

Evaluate a proposed action against authority, the Intent, policy and optional counterparty context.

  • Paid · Open

ECZ-ID Intent Control evaluates a proposed action before it happens — against the identity's authority, its authorised Intent, your policy and, where you supply it, counterparty context — and records the decision with its basis. Every decision is EVALUATED, never ENFORCED, unless an inline enforcement point reports mediating the action. The Intent + Intent Control plans put the authorised boundary and its runtime evaluation in one plan.

For an MCP server: For an MCP server: evaluate a proposed tool call against the server's Intent and your policy before the call is made, and keep the EVALUATED decision.

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 agent is about to call a tool on an MCP server. Intent Control evaluates that call against the server's authority, its Intent and your policy, and returns a decision your gateway or client can use.

The decision is EVALUATED: Intent Control stays outside the execution path, and enforcement stays with the runtime that mediates the call.

ECZ-ID Intent Control: fit, outcomes and contents

Best for

  • MCP providers and platform teams that want a recorded decision on a proposed tool call.
  • Organisations writing policy for what their agents and servers may do.
  • Teams that already define Intents and want proposed actions evaluated against them.

What you get out of it

  • A recorded decision for each proposed action, with its basis.
  • Policy expressed once and evaluated consistently across protected entities.
  • A clear line between an EVALUATED decision and an ENFORCED one.

What is included

  • Protected entities, hosted decisions and policy syncs, set by the tier.
  • Evaluation against authority, the Intent, policy and optional counterparty context.
  • Intent + Intent Control plans: both services in one plan — the authorised boundary and its runtime evaluation.
  • The same product across all seven Passport families.

How it works

  1. Define the Intent and the policy for a protected entity.

  2. Before acting, a caller submits the proposed action for evaluation.

  3. Intent Control returns a decision with its basis, recorded as EVALUATED.

  4. Your runtime, gateway or enforcement point decides whether to act on it; only an inline enforcement point that reports mediating the action makes it ENFORCED.

What it is not

  • A decision is EVALUATED, never ENFORCED, unless an inline enforcement point reports mediating the action.
  • Payment authorises nothing, and a Passport is not an Intent authorisation.
  • Intent Control complements OAuth, MCP authorization and runtime mediation; it replaces none of them and stays outside the execution path.

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