# gns_get_compliance_report

Returns a full EU AI Act compliance report for a GNS agent, including trust score, chain verification, Merkle epoch proofs, delegation certificate, and regulatory status.

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

## Facts

- Tool: `gns_get_compliance_report`
- 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 |
| --- | --- | --- | --- |
| `agentHandle` | string | no | GNS handle of the agent (e.g. energy@italy-geiant) |

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

## Why gns_get_compliance_report is rated Low

This tool queries and retrieves compliance information for an AI agent. It has no side effects—it does not create, modify, delete, or execute external operations. Even though the data concerns governance and compliance, the tool itself only reads/returns existing information. Risk is low: misuse would mean retrieving compliance reports, which has minimal blast radius.

From the tool's own definition: "Tool name contains 'get' and description uses 'returns' — indicates retrieval of compliance data with no modification or destructive action. Returns report data: trust score, chain verification results, proofs, certificate, and regulatory status."

## Use case

AI agents call gns_get_compliance_report 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_compliance_report": {}
  }
}
```

## 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_trust_score` — Read — https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-get-trust-score.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