related_keywords

THE RISK

Low Risk

Why related_keywords needs a policy

This tool queries the Semrush API to fetch keyword data. It retrieves information without creating, modifying, deleting, or executing any actions. The operation is read-only with no side effects on external systems or data.

From the tool's definition Tool description states it will 'Get related keywords and suggestions' — a retrieval operation with no modification, deletion, or execution of external systems.

Documented attack patterns abuse exactly the kind of access related_keywords gives an agent:

POLICY

How to control related_keywords

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 related_keywords:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "related_keywords": {}
  }
}

related_keywords is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Semrush MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Semrush MCP Server tools

Read backlinks_overview Get backlinks overview for a domain or URL. Target type can be root_domain, domain, or url Read competitor_research Find organic competitors for a domain Read domain_adwords Get paid search (Google Ads) keywords for a domain Read domain_organic_search Get organic search keywords for a domain Read domain_overview Get domain analytics overview including organic traffic, keywords, and authority score Read keyword_overview Get keyword metrics including search volume, difficulty, and CPC

All 7 Semrush MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about related_keywords

What does the related_keywords tool do? +

Get related keywords and suggestions for a seed keyword. It is categorised as a Read tool in the Semrush MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on related_keywords? +

Register the Semrush MCP Server MCP server in PolicyLayer and add a rule for related_keywords: 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.

What risk level is related_keywords? +

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

Can I rate-limit related_keywords? +

Yes. Add a rate_limit block to the related_keywords 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 related_keywords completely? +

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

related_keywords 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.

Enforce policy on every Semrush MCP Server tool call.

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.

CHECK YOUR STACK →