get_keyword_gap
Get the keyword gap for a cataloged domain: phrases a tracked competitor holds a position for in our stored captures where this domain holds none ("absent"), or holds one at least 20 places further back ("behind"). Claimed domains only, computed from captures already on disk. Nothing is fetched a...
This record as markdown: /tools/com-groundedaeo-grounded-aeo/get-keyword-gap.md
What get_keyword_gap does on Grounded Aeo
AI agents call get_keyword_gap 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_keyword_gap is rated Low
This tool performs SEO analysis by comparing keyword rankings between domains using pre-computed, stored data. It retrieves and queries existing capture data to identify keyword gaps. No data is modified, created, deleted, or written; no external operations are triggered; and no financial transactions occur. The operation is purely informational retrieval from an internal data store.
From the tool's definition Tool description states: "Get the keyword gap...", "Nothing is fetched and nothing is spent", "computed from captures already on disk".
Attacks that exploit this kind of access
The rule that runs get_keyword_gap 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_keyword_gap, this is the rule to start with:
get_keyword_gap 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_keyword_gap call is checked against it from then on.
Questions about get_keyword_gap
Get the keyword gap for a cataloged domain: phrases a tracked competitor holds a position for in our stored captures where this domain holds none ("absent"), or holds one at least 20 places further back ("behind"). Claimed domains only, computed from captures already on disk. Nothing is fetched and nothing is spent. The stored lists are a SAMPLE of each domain's footprint (the top rows a capture kept), so absence here is absence from our sample, never from public search; the response carries that sentence and it must be repeated wherever the result is shown. Positions are ranking footprint, never traffic. It is categorised as a Read tool in the Grounded Aeo MCP Server, which means it retrieves data without modifying state.
get_keyword_gap 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_keyword_gap: 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_keyword_gap 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_keyword_gap 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_keyword_gap. 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_keyword_gap 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