Get keyword difficulty for a keyword using ReviewWeb.site API.
AI agents call seo_keyword_difficulty to retrieve information from ReviewWebsite 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 SEO metric information (keyword difficulty score) from an API without altering state, creating side effects, or executing commands. It is analogous to a search or query function that returns read-only data, making it a Read category tool with low severity.
From the tool's definition Tool description states it 'Get[s] keyword difficulty for a keyword' — a data retrieval operation with no modification, creation, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access seo_keyword_difficulty gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReviewWebsite MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for seo_keyword_difficulty:
{
"version": "1",
"default": "deny",
"tools": {
"seo_keyword_difficulty": {}
}
}seo_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 a keyword using ReviewWeb.site API. It is categorised as a Read tool in the ReviewWebsite MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ReviewWebsite MCP Server MCP server in PolicyLayer and add a rule for seo_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 ReviewWebsite MCP Server. Nothing to install.
seo_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 seo_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 seo_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.
seo_keyword_difficulty is provided by the ReviewWebsite MCP Server MCP server (mrgoonie/reviewwebsite-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReviewWebsite 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.
16 ReviewWebsite MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.