Get keyword difficulty for the specified keyword. Returns difficulty score and SERP analysis.
AI agents call keyword_difficulty 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 queries SEO data (keyword difficulty metrics and SERP analysis) without creating, modifying, deleting, or executing anything. It is a straightforward read-only data retrieval function. Even if misused by an AI agent, the worst outcome would be excessive API queries, not data loss or system compromise. Low severity due to minimal blast radius.
From the tool's definition Tool description states it 'Get[s] keyword difficulty' and 'Returns difficulty score and SERP analysis' — purely retrieval operations with no modification, deletion, or execution of external systems.
Documented attack patterns abuse exactly the kind of access keyword_difficulty 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 keyword_difficulty:
{
"version": "1",
"default": "deny",
"tools": {
"keyword_difficulty": {}
}
}keyword_difficulty 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.
Get keyword difficulty for the specified keyword. Returns difficulty score and SERP analysis. 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 keyword_difficulty: 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.
keyword_difficulty 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 keyword_difficulty 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 keyword_difficulty. 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.
keyword_difficulty 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.