AI agents call semrush_traffic_summary 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 traffic summary analytics data from Semrush's Trends API. It is a query/fetch operation that returns domain traffic information with no capability to modify, delete, or execute external operations. The blast radius of misuse is limited to unauthorized access to competitive intelligence data, which constitutes a Read-category risk.
From the tool's definition Tool name and description indicate data retrieval: 'Get traffic summary data for domains' with no mention of modifications, deletions, or side effects. Requires API access but performs read-only analytics queries.
Attacks that exploit this kind of access
Get traffic summary data for domains (requires .Trends API access). 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_traffic_summary: 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_traffic_summary 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_traffic_summary 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_traffic_summary. 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_traffic_summary 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 →