Research a keyword across every configured AI engine. Returns volume, intent, related
AI agents call research_keyword to retrieve information from SurfRank 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 analytics data about keywords from AI engines without creating, modifying, deleting, or executing any actions. It has no side effects and poses minimal risk if misused — the worst outcome would be querying unintended keywords, which is harmless. It clearly falls into the Read category.
From the tool's definition The tool description states it 'Research a keyword' and 'Returns volume, intent, related' — these are data retrieval operations with no modification or execution capabilities.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Research a keyword across every configured AI engine. Returns volume, intent, related. It is categorised as a Read tool in the SurfRank MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SurfRank MCP Server MCP server in PolicyLayer and add a rule for research_keyword: 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 SurfRank MCP Server. Nothing to install.
research_keyword 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 research_keyword 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 research_keyword. 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.
research_keyword is provided by the SurfRank MCP Server MCP server (surfrankai/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 →