search_robot_keywords
AI agents call search_robot_keywords 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.
Searching indexed keyword metadata is a read-only retrieval operation. The tool queries stored metadata in SQLite to help draft test cases, which has no side effects or data modification. The empty description lowers confidence slightly, but the tool name and server purpose clearly indicate a lookup/search function rather than code execution, data modification, or destructive operations.
From the tool's definition Tool name 'search_robot_keywords' indicates a search operation; server context shows it indexes Robot Framework files and provides metadata retrieval for LLM assistance.
Attacks that exploit this kind of access
search_robot_keywords. 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 search_robot_keywords: 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.
search_robot_keywords 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 search_robot_keywords 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 search_robot_keywords. 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.
search_robot_keywords 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 →