gns_verify_chain
Verify the cryptographic integrity of an agent's breadcrumb chain. Returns { is_valid, block_count, issues[] } plus epoch Merkle roots. A valid chain proves no audit records have been tampered with.
This record as markdown: /tools/com-geiant-mcp-agentcore/gns-verify-chain.md
What gns_verify_chain does on Mcp Agentcore
AI agents call gns_verify_chain 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 |
|---|---|---|---|
agent_pk | string | — | Ed25519 public key (64 hex chars). Omit for own agent. |
Parameters from the server's own tool schema.
Why gns_verify_chain is rated Low
gns_verify_chain is a cryptographic verification function that queries and validates the integrity of existing chain data. It has no side effects—it only inspects and reports on audit record integrity.
From the tool's definition Tool performs verification and returns data ('Verify the cryptographic integrity', 'Returns { is_valid, block_count, issues[] }'); it reads and checks existing audit records without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs gns_verify_chain 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_verify_chain, this is the rule to start with:
gns_verify_chain 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_verify_chain call is checked against it from then on.
Questions about gns_verify_chain
Verify the cryptographic integrity of an agent's breadcrumb chain. Returns { is_valid, block_count, issues[] } plus epoch Merkle roots. A valid chain proves no audit records have been tampered with. It is categorised as a Read tool in the Mcp Agentcore MCP Server, which means it retrieves data without modifying state.
gns_verify_chain accepts 1 parameter: agent_pk. 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_verify_chain: 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_verify_chain 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_verify_chain 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_verify_chain. 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_verify_chain 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