List quick tests, optionally filtered by project.
AI agents call list_quick_tests 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 performs a read-only operation—it lists/retrieves quick test data with optional filtering. It does not create, modify, delete, or execute tests. The 'list' verb and passive retrieval nature, combined with the filtering parameters, confirm this is a Read category tool. The severity is low as listing test metadata poses minimal security risk and has no external side effects.
From the tool's definition Tool name 'list_quick_tests' and description 'List quick tests, optionally filtered by project' indicate a retrieval operation that queries existing test data without modification or execution of tests.
Attacks that exploit this kind of access
List quick tests, 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_quick_tests: 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_quick_tests 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_quick_tests 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_quick_tests. 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_quick_tests 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 →