agent_passport
Paid ($10 USDC on Algorand). Identity, KYA, reputation and the risk verdict for one agent in a single document. Saved for 24 hours: asking again returns the saved answer and pays nothing.
This record as markdown: /tools/a-identity-trust-mcp/agent-passport.md
What agent_passport does on Trust
AI agents call agent_passport to retrieve information from Trust without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
agentId | string | Yes | The agent to check: an ERC-8004 token id ("#849980"), a CAIP id, or an owner address. |
Parameters from the server's own tool schema.
Why agent_passport is rated Low
Even though agent_passport only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs agent_passport safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trust, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agent_passport, this is the rule to start with:
agent_passport is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Trust, apply this rule, and every agent_passport call is checked against it from then on.
Questions about agent_passport
Paid ($10 USDC on Algorand). Identity, KYA, reputation and the risk verdict for one agent in a single document. Saved for 24 hours: asking again returns the saved answer and pays nothing. It is categorised as a Read tool in the Trust MCP Server, which means it retrieves data without modifying state.
agent_passport accepts 1 parameter: agentId. Required: agentId. The full parameter table on this page comes from the server's own tool schema.
Register the Trust MCP server in PolicyLayer and add a rule for agent_passport: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Trust. Nothing to install.
agent_passport is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the agent_passport rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for agent_passport. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
agent_passport is provided by the Trust MCP server (@a-identity/trust-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trust, and thousands of servers like it.
This server
Across the catalogue