rank_keyword_candidates
AI agents call rank_keyword_candidates to retrieve information from RobotWS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the naming pattern and server's primary function (indexing and metadata storage for generation context) strongly suggest this tool reads/queries the SQLite index to rank keyword candidates. No write, execute, or destructive operations are evident. Confidence is moderate (0.75) due to the missing description, but the read category is justified by context and sibling tool patterns.
From the tool's definition Tool name 'rank_keyword_candidates' suggests querying or retrieving keyword metadata. Server context indicates it indexes Robot Framework files and stores metadata in SQLite.
Attacks that exploit this kind of access
rank_keyword_candidates. It is categorised as a Read tool in the RobotWS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RobotWS MCP Server MCP server in PolicyLayer and add a rule for rank_keyword_candidates: 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 RobotWS MCP Server. Nothing to install.
rank_keyword_candidates 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 rank_keyword_candidates 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 rank_keyword_candidates. 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.
rank_keyword_candidates is provided by the RobotWS MCP Server MCP server (stella555359/robotws_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 →