List past keyword research runs, optionally filtered by project.
AI agents call list_keyword_research 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 and queries existing keyword research data. The verb 'list' and the passive framing ('past keyword research runs') confirm it performs read-only operations with no capability to modify, delete, or execute external actions. The optional filtering parameter does not change the fundamental read-only nature of the operation.
From the tool's definition Tool name 'list_keyword_research' and description 'List past keyword research runs, optionally filtered by project' indicate retrieval of historical data without modification or side effects.
Attacks that exploit this kind of access
List past keyword research runs, optionally filtered by project. 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 list_keyword_research: 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.
list_keyword_research 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 list_keyword_research 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 list_keyword_research. 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.
list_keyword_research 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 →