AI agents call semrush_competitors 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 retrieves domain competitor information from the Semrush API. It is a read-only query operation with no side effects, no code execution, no data modification, and no irreversible actions. The blast radius of misuse is minimal - an agent could retrieve competitor data for domains it shouldn't analyze, but this causes no damage to systems or data.
From the tool's definition Tool description states 'Get competitors for a specific domain in organic search' - a query operation that retrieves and presents existing competitive intelligence data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get competitors for a specific domain in organic search. 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_competitors: 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_competitors 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_competitors 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_competitors. 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_competitors 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 →