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.
This record as markdown: /tools/com-geiant-mcp-agentcore/gns-get-compliance-report.md
What gns_get_compliance_report does on Mcp Agentcore
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
agentHandle | string | — | GNS handle of the agent (e.g. energy@italy-geiant) |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs gns_get_compliance_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Agentcore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gns_get_compliance_report, this is the rule to start with:
gns_get_compliance_report 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 Mcp Agentcore, apply this rule, and every gns_get_compliance_report call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Mcp Agentcore MCP Server, which means it retrieves data without modifying state.
gns_get_compliance_report accepts 1 parameter: agentHandle. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Agentcore MCP server in PolicyLayer and add a rule for gns_get_compliance_report: 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 Mcp Agentcore. Nothing to install.
gns_get_compliance_report 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 gns_get_compliance_report 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 gns_get_compliance_report. 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.
gns_get_compliance_report is provided by the Mcp Agentcore MCP server (https://packagesmcp-perception-production.up.railway.app/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Agentcore, and thousands of servers like it.
This server
Across the catalogue