check_serp
Check the live Google search results for any keyword: the top 10 organic results (rank, domain, title), the People Also Ask questions, related searches, and which non-organic blocks occupy the page, so you can tell whether a query has an AI Overview or local pack slot at all. Public data, no cata...
This record as markdown: /tools/com-groundedaeo-grounded-aeo/check-serp.md
What check_serp does on Grounded Aeo
AI agents call check_serp 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 |
|---|---|---|---|
keyword | string | Yes | Search query, e.g. "roof repair denver" |
Parameters from the server's own tool schema.
Why check_serp is rated Low
The check_serp tool performs read-only retrieval of publicly available Google search results data (organic rankings, People Also Ask, related searches, non-organic blocks). It accesses public information with no capability to modify, create, delete, or execute operations.
From the tool's definition Tool description states: 'Check the live Google search results for any keyword' and 'Public data, no catalog entry required.' The tool retrieves and queries SERP data with no side effects mentioned.
Attacks that exploit this kind of access
The rule that runs check_serp 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_serp, this is the rule to start with:
check_serp 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_serp call is checked against it from then on.
Questions about check_serp
Check the live Google search results for any keyword: the top 10 organic results (rank, domain, title), the People Also Ask questions, related searches, and which non-organic blocks occupy the page, so you can tell whether a query has an AI Overview or local pack slot at all. Public data, no catalog entry required. A keyword with genuinely no results returns empty arrays, which is a real finding, not an error. It is categorised as a Read tool in the Grounded Aeo MCP Server, which means it retrieves data without modifying state.
check_serp accepts 1 parameter: keyword. Required: keyword. 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_serp: 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_serp 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_serp 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_serp. 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_serp 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