get_engine_visibility
Get the per-engine picture for a cataloged domain: whether each AI engine's crawler is allowed by robots.txt to read the site at all, and how many of the tracked questions that engine cited it on. Claimed domains only. Nothing is assumed: an engine with no crawl measurement reports can_read:null ...
This record as markdown: /tools/com-groundedaeo-grounded-aeo/get-engine-visibility.md
What get_engine_visibility does on Grounded Aeo
AI agents call get_engine_visibility 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 | Company domain, e.g. acme.com |
Parameters from the server's own tool schema.
Why get_engine_visibility is rated Low
This tool queries and retrieves existing data about crawler permissions and citation metrics for a domain. It performs informational lookups with no side effects, state changes, or irreversible actions. The emphasis on reporting measured values or null (avoiding assumptions) further confirms read-only behavior.
From the tool's definition Tool description states it 'Get[s] the per-engine picture' including whether crawlers are 'allowed' and 'how many' citations—purely retrieval operations.
Attacks that exploit this kind of access
The rule that runs get_engine_visibility 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 get_engine_visibility, this is the rule to start with:
get_engine_visibility 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 get_engine_visibility call is checked against it from then on.
Questions about get_engine_visibility
Get the per-engine picture for a cataloged domain: whether each AI engine's crawler is allowed by robots.txt to read the site at all, and how many of the tracked questions that engine cited it on. Claimed domains only. Nothing is assumed: an engine with no crawl measurement reports can_read:null ("not measured", never an assumed allow), and an engine with no citation checks reports cited/tracked null ("untested", never a miss and never zero). Access and citations only: this says nothing about traffic. It is categorised as a Read tool in the Grounded Aeo MCP Server, which means it retrieves data without modifying state.
get_engine_visibility 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 get_engine_visibility: 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.
get_engine_visibility 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 get_engine_visibility 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 get_engine_visibility. 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.
get_engine_visibility 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