list_test_cases
List test cases in a test project. Optional filters: suite (ID or name), assignee (name or email).
This record as markdown: /tools/dugynoo-huly-mcp/list-test-cases.md
What list_test_cases does on Huly
AI agents call list_test_cases to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_test_cases is rated Low
This tool retrieves and queries test case data from a test project with optional filter parameters. It has no side effects, does not modify or delete data, and does not execute external operations. It is a straightforward data retrieval operation fitting the Read category with low severity, as it only exposes existing data without risk of unintended consequences.
From the tool's definition Tool name 'list_test_cases' with description 'List test cases in a test project' performs data retrieval with optional filtering parameters (suite, assignee). Uses verb 'List' which is explicitly a Read operation with no modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs list_test_cases safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_test_cases, this is the rule to start with:
list_test_cases is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every list_test_cases call is checked against it from then on.
Questions about list_test_cases
List test cases in a test project. Optional filters: suite (ID or name), assignee (name or email). It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for list_test_cases: 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 Huly. Nothing to install.
list_test_cases 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 list_test_cases 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 list_test_cases. 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.
list_test_cases is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue