# reputation_score

Paid ($2 USDC on Algorand). A deterministic 0-1000 reputation with its breakdown, a Sybil signal, and the latest on-chain attestation of the score. Saved for 24 hours: asking again returns the saved answer and pays nothing.

Agent View of the PolicyLayer registry record for `reputation_score`. HTML page: https://policylayer.com/tools/a-identity-trust-mcp/reputation-score

## Facts

- Tool: `reputation_score`
- Server: Trust (`@a-identity/trust-mcp`) — https://policylayer.com/tools/a-identity-trust-mcp.md
- Install: `npx -y @a-identity/trust-mcp`
- Homepage: https://www.npmjs.com/package/@a-identity/trust-mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "reputation_score",
    "arguments": {
      "agentId": "<agentId>"
    }
  }
}
```

## Why reputation_score is rated Low

Even though reputation_score 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.

## Use case

AI agents call reputation_score 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Trust:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "reputation_score": {}
  }
}
```

## Other tools on Trust (8)

- `agent_batch_audit` — Read — https://policylayer.com/tools/a-identity-trust-mcp/agent-batch-audit.md
- `agent_passport` — Read — https://policylayer.com/tools/a-identity-trust-mcp/agent-passport.md
- `check_batch` — Read — https://policylayer.com/tools/a-identity-trust-mcp/check-batch.md
- `check_before_pay` — Read — https://policylayer.com/tools/a-identity-trust-mcp/check-before-pay.md
- `pay_check` — Read — https://policylayer.com/tools/a-identity-trust-mcp/pay-check.md
- `price_quote` — Read — https://policylayer.com/tools/a-identity-trust-mcp/price-quote.md
- `risk_check` — Read — https://policylayer.com/tools/a-identity-trust-mcp/risk-check.md
- `verify_agent` — Read — https://policylayer.com/tools/a-identity-trust-mcp/verify-agent.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=a-identity-trust-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a-identity-trust-mcp
