create_test_plan
Create a test plan in a project. Idempotent: returns existing plan if one with the same name exists (created=false).
This record as markdown: /tools/dugynoo-huly-mcp/create-test-plan.md
What create_test_plan does on Huly
AI agents use create_test_plan to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.
Why create_test_plan is rated Medium
This tool creates test plan resources within a project management system. While creation is a reversible write operation (plans can typically be deleted), it modifies project state and could impact team workflows if misused by an AI agent to create numerous test plans.
From the tool's definition Tool name 'create_test_plan' and description 'Create a test plan in a project' explicitly indicates creation of new data.
Attacks that exploit this kind of access
The rule that runs create_test_plan 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 create_test_plan, this is the rule to start with:
create_test_plan stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_test_plan call is checked against it from then on.
Questions about create_test_plan
Create a test plan in a project. Idempotent: returns existing plan if one with the same name exists (created=false). It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huly MCP server in PolicyLayer and add a rule for create_test_plan: 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.
create_test_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_test_plan 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 create_test_plan. 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.
create_test_plan 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