Skip to content
EcoCitizenZ
Agent plugin · Support

ECZ-ID Agent Trust

Support

This page covers the ECZ-ID Agent Trust agent plugin — the package eczid-agent-trust, published at version 0.1.1. It tells you how to reach us, what to include so a problem can be reproduced, and how security reports are handled differently from ordinary support.

Applies to:
eczid-agent-trust 0.1.1
Effective date:
3 September 2026

In short

  • Support runs by email: support@ecocitizenz.com. There is no account to create and no support portal to sign in to.
  • The plugin is free, and support for it is free. No support contract is required, and none is offered for it.
  • The review reports what an agent surface declares. It grants no authority, removes none, and establishes nobody's identity — see what it cannot establish.
  • Never send passwords, API keys, tokens, certificates or any other secret. Nothing about this product needs one.
  • Suspected security vulnerabilities go to the same address but under the security reporting route, not the ordinary support route.
  • We publish no response-time commitment for this free plugin, so this page does not imply one.

What the plugin does

ECZ-ID Agent Trust adds one skill, agent-trust-review, to an agent host. When you ask what the agents in a workspace can reach, the agent runs a bundled review script over the folder you point it at, then reports which classes of evidence it found, which it did not, why each matters and what to review next.

The review works from file names and paths only. It looks for these classes of evidence:

  • Agent manifest / agent card (primary evidence class)
  • MCP servers the agent can reach (primary evidence class)
  • Permissions / allowlist policy (primary evidence class)
  • Agent instructions / rules (supporting evidence class)
  • Declared tools / functions (supporting evidence class)
  • Agent framework surface (supporting evidence class)
  • ECZ-ID public proof reference (supporting evidence class)

It does not open any of those files. So it can tell you that an agent manifest or a permissions policy exists where a reviewer would expect one, and it cannot tell you what either of them says.

Results are reported as EVIDENCE OBSERVED, EVIDENCE NOT OBSERVED, REVIEW RECOMMENDED and REVIEW REQUIRED, with a Review Priority of LOW, NORMAL, ELEVATED, HIGH and the reasons that produced it. The Review Priority is deterministic: the same file listing always gives the same result. It is not a score, a grade, a pass mark or a verdict.

The Privacy page sets out exactly what the plugin reads and what it does not. The Terms page sets out the basis on which you may use it.

What a review can and cannot establish

The shipped skill puts it in one line: inspection only, filename and path only, and nothing here grants or removes authority. It is worth unpacking, because “agent trust” could easily be read as a stronger claim than the product makes.

What it can tell you. That a workspace contains a file whose name and location match what a reviewer would look for — an agent manifest, an instructions file, a permissions policy, an MCP configuration, a tool definition, a framework surface, a public proof reference — and where that file is.

What it cannot tell you. Who operates the agent. Whether the operator is who they say they are. Whether the declared capabilities are the real ones. Whether a permissions policy is actually applied at run time, or merely present in the repository. Whether an agent behaves as its instructions describe. None of that is visible from a file listing, and the plugin does not attempt it.

Identity assurance is a different thing entirely: it is produced by the ECZ-ID platform through TrustOps and read from the public Resolver, and it attaches to a credential, not to a file in a repository. Observing an ecz-agent.json tells you a reference exists. Checking it in the Resolver tells you what the public record currently says. Those are two steps, and the review is only the first.

Things worth checking first

Most reports we can act on quickly come down to one of these, and each is faster to check than to describe in an email.

  • An agent surface was not observed in a workspace that has one. The review skips node_modules, dist, build and similar generated directories, and it skips hidden dot-entries other than an allowlist. That allowlist covers the host directories where agent instructions and permissions normally live and is listed in full on the Privacy page. A surface stored outside it will not be observed.
  • The review stopped short in a large repository. Traversal is bounded by design, so a review cannot run away on a very large tree. Point it at the sub-project you care about rather than at a monorepo root.
  • The host cannot find the skill. Confirm the plugin is installed and enabled in that host, and that a Node.js runtime is available — the bundled review script runs on Node and has no other dependency.
  • The Verifier tools are not available. This package also declares the ECZ-ID Verifier server, @ecocitizenz/ecz-id-mcp-verifier@0.9.0, which only hosts that run local stdio MCP servers will launch. Without it the review still runs; what you lose is the ability to check a public proof reference it found. See the MCP Verifier support page.
  • You want to see exactly what the review did. The script is short, readable and has no build step. Read review.mjs, or run it yourself with --json for the machine-readable projection.

Getting support

Email support@ecocitizenz.com. This is the support route for every EcoCitizenz product, so please name ECZ-ID Agent Trust in the subject line.

A report we can act on usually contains:

  • the plugin name and version — eczid-agent-trust 0.1.1;
  • the agent host and its version, and how the plugin was installed there — which marketplace, or a local copy;
  • your operating system and Node.js version;
  • what you asked the agent to do, and what you expected to happen;
  • what actually happened, quoted rather than summarised;
  • any error text in full and, if the review ran, the --json output — the single most useful attachment for a detection problem;
  • for a detection problem, the file name and path you expected to be observed. The path is enough. We do not need the file, and we do not want your agent instructions or your permissions policy.

If the repository is private, please do not send it. A redacted directory listing, or a small public example that reproduces the same behaviour, is more useful and safer for both of us.

What never to send

Nothing about diagnosing this plugin requires a credential, and we will never ask you for one. Please do not include, in a message, an attachment or a screenshot:

  • passwords, passphrases or PINs;
  • API keys, access tokens, session cookies or bearer tokens;
  • private keys, certificates, keystores or signing material;
  • .env files, CI secrets or cloud credentials;
  • customer personal data, or confidential source code you are not free to share.

If you believe you have already sent us a secret, rotate it immediately — that is the only reliable remedy — and then tell us, so we can delete the message on our side.

Reporting a security vulnerability

Security reports are handled separately from ordinary support. If you believe you have found a vulnerability in this plugin, in the review script it ships, or in the ECZ-ID Verifier server it declares, or in another EcoCitizenz service, report it to support@ecocitizenz.com with security report in the subject line, rather than raising it in a public issue.

A useful security report describes the affected component and version, the conditions needed to reproduce the issue, the impact you observed, and anything you think we would otherwise miss. Please give us a reasonable opportunity to respond before disclosing publicly, where earlier disclosure would create material risk for users.

EcoCitizenz supports good-faith security research. When testing, please do not access customer data unnecessarily, destroy or alter data, disrupt production systems, perform denial-of-service testing, or exploit an issue beyond what is reasonably required to demonstrate it. Those conditions are set out in the security research section of the Terms.

We do not operate a paid bug-bounty programme for this plugin, and this page offers no reward.

Reporting misuse of ECZ-ID material

Misuse is not the same as a vulnerability. If you have seen a copied manifest on an unrelated origin, an impersonated operator, a stale or misleading proof reference, or a page imitating ECZ-ID verification, use the abuse report route. Reports are reviewed. They do not by themselves decide truth or change any credential state.

Source, and the same review elsewhere

The plugin is open source, so you do not have to take any statement on these pages on trust — you can read every line it runs.

  • The published plugin package — manifest, skill, review script and server declaration.
  • The ECZ-ID plugins page — how to install this and the other ECZ-ID plugins in your agent host.
  • Agent Trust documentation — what an agent should declare, how authority is bounded, and how a free ECZ-ID Agent Passport gives an agent you operate a public, resolver-checkable identity.
  • Agent Identity and KYA guidance — how public proof about agents actually works, which the review only points at.
  • The same detectors, guidance and Review Priority also ship in the free VS Code extension ECZ-ID Agent Trust, on the Visual Studio Marketplace and Open VSX. That extension is a separate product with its own release cycle; these pages describe the plugin.

What support does not cover

  • We can explain what the review observed and why. We cannot tell you whether an agent is safe to run or trustworthy, and nothing we send you is a safety or identity determination.
  • We do not review your agent manifests, instructions or permissions for you, and the plugin does not read them. Whether the authority they describe is appropriate is a judgement for you.
  • We cannot confirm who operates an agent. Public identity is produced through TrustOps and read from the Resolver; support cannot shortcut it or vouch for anyone.
  • No support answer certifies, approves or guarantees an agent, workspace, product or organisation, and an ELEVATED or HIGH Review Priority does not mean that anything is unsafe.
  • The Authority Graph and other Pro capabilities run in the VS Code extension under a separate licence. This plugin does not include them.

Publisher

ECZ-ID Agent Trust is published by EcoCitizenz Ltd, trading as EcoCitizenz, company number 17348848, registered in England and Wales.

66 Paul StreetLondon EC2A 4NAUnited KingdomContact: support@ecocitizenz.com