check_aeo_record
Check any domain (cataloged or not) for a v=AEO1 DNS record at _aeo.<domain>, the open standard (aeorecord.org) declaring whether a verified fact record exists and at what trust tier. Verifies the Ed25519 sig= against the live catalog content when present.
This record as markdown: /tools/com-groundedaeo-grounded-aeo/check-aeo-record.md
What check_aeo_record does on Grounded Aeo
AI agents call check_aeo_record to retrieve information from Grounded Aeo 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 |
|---|---|---|---|
domain | string | Yes |
Parameters from the server's own tool schema.
Why check_aeo_record is rated Low
This tool queries DNS records and validates signatures—pure information retrieval with no side effects. No data is written, modified, or deleted; no code is executed; no irreversible actions occur. The verification step is a read-only validation. Severity is low because a miscall merely returns incorrect information about a domain's AEO certification status, with no operational impact.
From the tool's definition check_aeo_record performs DNS lookups and verification of existing v=AEO1 records without modification. The description states it 'checks' and 'verifies' but does not create, modify, delete, or execute operations.
Attacks that exploit this kind of access
The rule that runs check_aeo_record safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Grounded Aeo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_aeo_record, this is the rule to start with:
check_aeo_record 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 Grounded Aeo, apply this rule, and every check_aeo_record call is checked against it from then on.
Questions about check_aeo_record
Check any domain (cataloged or not) for a v=AEO1 DNS record at _aeo.<domain>, the open standard (aeorecord.org) declaring whether a verified fact record exists and at what trust tier. Verifies the Ed25519 sig= against the live catalog content when present. It is categorised as a Read tool in the Grounded Aeo MCP Server, which means it retrieves data without modifying state.
check_aeo_record accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Grounded Aeo MCP server in PolicyLayer and add a rule for check_aeo_record: 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 Grounded Aeo. Nothing to install.
check_aeo_record 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 check_aeo_record 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 check_aeo_record. 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.
check_aeo_record is provided by the Grounded Aeo MCP server (https://groundedaeo.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Grounded Aeo, and thousands of servers like it.
This server
Across the catalogue