Compare keywords across domains (v1/domain/keywords/comparison)
AI agents call domainKeywordsReverseComparison to retrieve information from Seo Data Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries SEO data to compare keyword performance across multiple domains, which is a data retrieval and analysis operation with no side effects. No data is created, modified, deleted, or financial transactions are involved. The 'comparison' operation is analytical and read-only in nature.
From the tool's definition Tool performs 'Compare keywords across domains' via a read-only API endpoint (v1/domain/keywords/comparison). The operation retrieves and analyzes keyword data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Compare keywords across domains (v1/domain/keywords/comparison). It is categorised as a Read tool in the Seo Data Api MCP Server, which means it retrieves data without modifying state.
Register the Seo Data Api MCP server in PolicyLayer and add a rule for domainKeywordsReverseComparison: 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 Seo Data Api. Nothing to install.
domainKeywordsReverseComparison 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 domainKeywordsReverseComparison 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 domainKeywordsReverseComparison. 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.
domainKeywordsReverseComparison is provided by the Seo Data Api MCP server (teake1404/seo-data-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →