AI agents call semrush_related_keywords to retrieve information from Semrush without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the Semrush API to retrieve keyword data related to a user-specified keyword. It performs a search/lookup operation that returns information without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could only retrieve keyword data that is already public through Semrush's service.
From the tool's definition Tool name 'semrush_related_keywords' and description 'Get related keywords for a specific keyword' indicate data retrieval with no modification or side effects. The verb 'get' is characteristic of Read operations.
Attacks that exploit this kind of access
Get related keywords for a specific keyword. It is categorised as a Read tool in the Semrush MCP Server, which means it retrieves data without modifying state.
Register the Semrush MCP server in PolicyLayer and add a rule for semrush_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. Nothing to install.
semrush_related_keywords 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 semrush_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.
Set action: deny in the PolicyLayer policy for semrush_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.
semrush_related_keywords is provided by the Semrush MCP server (superseoworld/semrush-mcp). 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 →