Fetch keyword questions (v1/keywords/questions)
AI agents call keywordsQuestions to retrieve information from Seo Data Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves keyword question data from SE Ranking's SEO API. It is a GET-like operation that queries and returns information without creating, modifying, deleting, or executing code. The blast radius of misuse is minimal: an agent could query excessive data or target competitors, but cannot alter state, move money, or trigger external actions. Classified as Read with low severity.
From the tool's definition Tool description states 'Fetch keyword questions' with endpoint v1/keywords/questions. The verb 'Fetch' indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Fetch keyword questions (v1/keywords/questions). It is categorised as a Read tool in the Seo Data Api MCP Server, which means it retrieves data without modifying state.
Register the Seo Data Api MCP server in PolicyLayer and add a rule for keywordsQuestions: 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 Data Api. Nothing to install.
keywordsQuestions 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 keywordsQuestions 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 keywordsQuestions. 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.
keywordsQuestions is provided by the Seo Data Api MCP server (teake1404/seo-data-api-mcp-server). 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 →