Get organic search keywords for a domain
AI agents call domain_organic_search to retrieve information from Semrush MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves SEO analytics data (organic search keywords) about a domain. It is a query operation that returns information without creating, modifying, deleting, or executing code. The blast radius of misuse is minimal—an agent could retrieve SEO data about any domain, but this does not compromise systems, finances, or cause irreversible harm. Classified as Read with low severity.
From the tool's definition Tool name is 'domain_organic_search' and description states 'Get organic search keywords for a domain' — the verb 'Get' indicates data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access domain_organic_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Semrush MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for domain_organic_search:
{
"version": "1",
"default": "deny",
"tools": {
"domain_organic_search": {}
}
} domain_organic_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get organic search keywords for a domain. It is categorised as a Read tool in the Semrush MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Semrush MCP Server MCP server in PolicyLayer and add a rule for domain_organic_search: 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 Semrush MCP Server. Nothing to install.
domain_organic_search 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 domain_organic_search 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 domain_organic_search. 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.
domain_organic_search is provided by the Semrush MCP Server MCP server (metehan777/semrush-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Semrush MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Semrush MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.