find_keyword_callers
AI agents call find_keyword_callers 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.
The tool retrieves or indexes information about keyword usage across Robot Framework files without modifying, executing, or deleting data. It is a read-only operation that supports test case generation by providing contextual information. The empty description reduces confidence slightly, but the naming and server purpose (metadata storage and context provision) strongly indicate a Read classification.
From the tool's definition Tool name 'find_keyword_callers' and server context indicate a search/query operation that locates where keywords are invoked in Robot Framework files.
Attacks that exploit this kind of access
find_keyword_callers. 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 find_keyword_callers: 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.
find_keyword_callers 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 find_keyword_callers 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 find_keyword_callers. 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.
find_keyword_callers 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 →