Check the estimated search traffic for any website. Returns traffic data, top pages, keywords, and countries.
AI agents call get_traffic to retrieve information from SEO Insights MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries publicly available SEO traffic metrics for a given website. It performs a lookup operation that returns informational data (traffic estimates, top pages, keywords, countries) without creating, modifying, deleting, or executing any operations. This is a standard read/retrieval operation with no side effects.
From the tool's definition Tool name is 'get_traffic' and description states it 'Check[s] the estimated search traffic for any website' and 'Returns traffic data, top pages, keywords, and countries.' The verb 'check' and 'returns' indicate data retrieval with no modification or…
Documented attack patterns abuse exactly the kind of access get_traffic gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SEO Insights MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_traffic:
{
"version": "1",
"default": "deny",
"tools": {
"get_traffic": {}
}
}get_traffic is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the estimated search traffic for any website. Returns traffic data, top pages, keywords, and countries. It is categorised as a Read tool in the SEO Insights MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SEO Insights MCP Server MCP server in PolicyLayer and add a rule for get_traffic: 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 SEO Insights MCP Server. Nothing to install.
get_traffic 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 get_traffic 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 get_traffic. 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.
get_traffic is provided by the SEO Insights MCP Server MCP server (mrgoonie/seo-insights-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SEO Insights MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 SEO Insights MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.