AI agents call semrush_traffic_sources 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 analytics data from Semrush's Trends API for a specified domain. It performs a query operation with no capability to modify, delete, or execute arbitrary actions. The blast radius of misuse is limited to potential exposure of competitive intelligence data, which constitutes a low severity risk.
From the tool's definition Tool name 'semrush_traffic_sources' and description 'Get traffic sources data for a domain' indicate a retrieval operation. The verb 'Get' and context of fetching analytics data confirm read-only functionality with no modifications, deletions, or side effects.
Attacks that exploit this kind of access
Get traffic sources data for a domain (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_sources: 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_sources 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_sources 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_sources. 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_sources 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 →