list_test_plans
List test plans in a test management project. Returns plan names and IDs. Requires project ID or name.
This record as markdown: /tools/dugynoo-huly-mcp/list-test-plans.md
What list_test_plans does on Huly
AI agents call list_test_plans 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_plans is rated Low
This tool retrieves and queries test plan metadata (names and IDs) from a test management project. It performs a read-only operation with no capability to modify, delete, or execute actions. The requirement for project ID/name is a filter parameter, not an indication of write or execute capability. Blast radius is minimal—incorrect usage returns no data or filtered results, with no adverse effects.
From the tool's definition Tool name is 'list_test_plans' and description states it 'List test plans' and 'Returns plan names and IDs'. The verb 'list' and 'returns' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_test_plans 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_plans, this is the rule to start with:
list_test_plans 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_plans call is checked against it from then on.
Questions about list_test_plans
List test plans in a test management project. Returns plan names and IDs. Requires project ID or name. 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_plans: 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_plans 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_plans 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_plans. 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_plans 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