update_test_case

Update a test case. Accepts test case ID or name. Only provided fields are modified. Set assignee to null to unassign.

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-case.md

What update_test_case does on Huly

AI agents use update_test_case 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 update_test_case is rated Medium

This tool modifies test case data (assignee, status, or other fields) but does not delete or irreversibly destroy data. The ability to set assignee to null shows field-level updates that are reversible. In a project management context, unauthorized test case modifications could impact testing workflows and quality assurance processes, justifying medium severity.

From the tool's definition Tool name 'update_test_case' and description 'Update a test case' indicates modification of existing data. Description specifies 'Only provided fields are modified', confirming reversible changes rather than deletion.

Questions about update_test_case

What does the update_test_case tool do? +

Update a test case. Accepts test case ID or name. Only provided fields are modified. Set assignee to null to unassign. 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_case? +

Register the Huly MCP server in PolicyLayer and add a rule for update_test_case: 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_case? +

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

Can I rate-limit update_test_case? +

Yes. Add a rate_limit block to the update_test_case 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_case completely? +

Set action: deny in the PolicyLayer policy for update_test_case. 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_case? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Huly's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.