# gns_get_trust_score

Get the current TierGate trust tier and score for an agent. Tiers: provisioned (0%) → observed (25%) → trusted (60%) → certified (85%) → sovereign (99%). Omit agent_pk to query the server's own agent.

Agent View of the PolicyLayer registry record for `gns_get_trust_score`. HTML page: https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-get-trust-score

## Facts

- Tool: `gns_get_trust_score`
- Server: Mcp Agentcore (`https://packagesmcp-perception-production.up.railway.app/mcp`) — https://policylayer.com/tools/com-geiant-mcp-agentcore.md
- Homepage: https://github.com/GNS-Foundation/geiant
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `agent_pk` | string | no | Ed25519 public key (64 hex chars). Omit for own agent. |

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": "gns_get_trust_score",
    "arguments": {}
  }
}
```

## Why gns_get_trust_score is rated Low

This tool queries and returns the current trust tier and score for an agent. It performs no creation, modification, deletion, code execution, or financial operations. The ability to omit the agent_pk parameter to query the server itself does not elevate the risk category, as it remains a simple read operation returning governance metadata.

From the tool's own definition: "Tool retrieves 'current TierGate trust tier and score' - a read-only query operation with no modification or side effects described."

## Use case

AI agents call gns_get_trust_score to retrieve information from Mcp Agentcore 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 Mcp Agentcore:

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

## Other tools on Mcp Agentcore (7)

- `perception_classify` — Execute — https://policylayer.com/tools/com-geiant-mcp-agentcore/perception-classify.md
- `perception_embed` — Other — https://policylayer.com/tools/com-geiant-mcp-agentcore/perception-embed.md
- `gns_get_compliance_report` — Read — https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-get-compliance-report.md
- `gns_verify_chain` — Read — https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-verify-chain.md
- `perception_fetch_tile` — Read — https://policylayer.com/tools/com-geiant-mcp-agentcore/perception-fetch-tile.md
- `gns_roll_epoch` — Write — https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-roll-epoch.md
- `perception_weather` — Write — https://policylayer.com/tools/com-geiant-mcp-agentcore/perception-weather.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=com-geiant-mcp-agentcore · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-geiant-mcp-agentcore