get_testcase_graph
AI agents call get_testcase_graph 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 or retrieve a graph representation of test case relationships from the indexed metadata. No evidence of side effects, modifications, deletions, code execution, or financial operations. The empty description lowers confidence slightly, but the semantic context (part of an analysis/generation helper server) and sibling tool patterns strongly suggest this is a Read operation.
From the tool's definition Tool name 'get_testcase_graph' indicates retrieval of graph data structure representing test cases. Server description emphasizes indexing, storing metadata, and providing 'generation context' to help with test case drafting—all read-oriented activities.
Attacks that exploit this kind of access
get_testcase_graph. 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_testcase_graph: 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_testcase_graph 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_testcase_graph 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_testcase_graph. 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_testcase_graph 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 →