recommend_template_steps
AI agents call recommend_template_steps 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 appears to query indexed metadata to recommend template steps for test case generation. This is a read-only advisory function with no side effects—it retrieves or suggests data without modifying state, executing code, or creating/deleting resources. The empty description lowers confidence slightly, but server purpose and naming pattern support Read classification.
From the tool's definition Tool name 'recommend_template_steps' suggests retrieval/suggestion of template patterns; server context indicates it indexes Robot Framework files and provides 'generation context to help Cursor's LLM draft testcases.' Sibling tools…
Attacks that exploit this kind of access
recommend_template_steps. 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 recommend_template_steps: 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.
recommend_template_steps 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 recommend_template_steps 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 recommend_template_steps. 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.
recommend_template_steps 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 →