update_test_plan

Update a test plan

SERVERHuly SOURCEdugynoo/huly-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dugynoo-huly-mcp/update-test-plan.md

WHAT IT DOES

What update_test_plan does on Huly

AI agents use update_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.

RISK

Why update_test_plan is rated Medium

This tool modifies existing test plan records reversibly within a project management system. It is Write rather than Execute because it performs a standard data mutation (update) on managed entities rather than executing arbitrary code or commands.

From the tool's definition Tool name 'update_test_plan' explicitly indicates modification of test plan data. Description states 'Update a test plan', confirming write operation on project management artifacts.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_test_plan, this is the rule to start with:

update_test_plan Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_test_plan": {
      "limits": [
        {
          "counter": "update_test_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every update_test_plan call is checked against it from then on.

FAQ

Questions about update_test_plan

What does the update_test_plan tool do? +

Update a test plan. 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.

How do I enforce a policy on update_test_plan? +

Register the Huly MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_test_plan? +

update_test_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_test_plan? +

Yes. Add a rate_limit block to the update_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.

How do I block update_test_plan completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_test_plan? +

update_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.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 218 Huly tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_plan_room on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →