get_case_pattern
AI agents call get_case_pattern 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 lowering confidence slightly, the tool name and server purpose (indexing and providing generation context) strongly suggest this retrieves or queries stored patterns for test cases. No indication of write, deletion, code execution, or financial operations. Classified as Read with low severity due to information-only nature.
From the tool's definition Tool name 'get_case_pattern' and server context indicate data retrieval from indexed Robot Framework metadata.
Attacks that exploit this kind of access
get_case_pattern. 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 get_case_pattern: 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.
get_case_pattern 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 get_case_pattern 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 get_case_pattern. 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.
get_case_pattern 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 →