Low Risk

keyword_overview

Keyword overview (Semrush type=phrase_this): search metrics for a single keyword phrase. Returns parsed rows with columns: Ph (phrase), Nq (search volume), Cp (CPC), Co (competition 0-1), Nr (number of organic results), Td (trend, last 12 months as |-separated values). Consumes your Semrush API u...

Part of the Semrush server.

keyword_overview is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE SEMRUSH →

Free to start. No card required.

AI agents call keyword_overview to retrieve information from Semrush without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though keyword_overview only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "keyword_overview": {}
  }
}

See the full Semrush policy for all 26 tools.

Get this rule live on your own Semrush server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SEMRUSH →

View all 26 tools →

These attack patterns abuse exactly the kind of access keyword_overview gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so keyword_overview only ever does what you allow.

SECURE SEMRUSH →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the keyword_overview tool do? +

Keyword overview (Semrush type=phrase_this): search metrics for a single keyword phrase. Returns parsed rows with columns: Ph (phrase), Nq (search volume), Cp (CPC), Co (competition 0-1), Nr (number of organic results), Td (trend, last 12 months as |-separated values). Consumes your Semrush API units.. It is categorised as a Read tool in the Semrush MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on keyword_overview? +

Register the Semrush MCP server in PolicyLayer and add a rule for keyword_overview: 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. Nothing to install.

What risk level is keyword_overview? +

keyword_overview is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit keyword_overview? +

Yes. Add a rate_limit block to the keyword_overview 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.

How do I block keyword_overview completely? +

Set action: deny in the PolicyLayer policy for keyword_overview. 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.

What MCP server provides keyword_overview? +

keyword_overview is provided by the Semrush MCP server (https://gateway.pipeworx.io/semrush/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Semrush tool call.

Deterministic rules across all 26 Semrush tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.