alm_update_test_case · HP ALM MCP Server MCP: Risk & Policy

WHAT IT DOES

What alm_update_test_case does on HP ALM MCP Server

AI agents use alm_update_test_case to create or update resources in HP ALM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HP ALM MCP Server environment.

WHY IT NEEDS A POLICY

Why alm_update_test_case needs a policy

This tool creates or modifies test case data reversibly—a core Write category behavior. While it affects QA artifacts, it does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). Severity is medium because unintended test case modifications could affect QA workflows and test coverage, but the impact is limited to internal QA processes and is reversible.

From the tool's definition Tool name 'alm_update_test_case' indicates modification of test case data within HP ALM/Quality Center. The verb 'update' signals a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

alm_update_test_case Rate-limited

alm_update_test_case 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": {
    "alm_update_test_case": {
      "limits": [
        {
          "counter": "alm_update_test_case_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches HP ALM MCP Server, so you can run agents against it safely.

FAQ

Questions about alm_update_test_case

What does the alm_update_test_case tool do? +

alm_update_test_case. It is categorised as a Write tool in the HP ALM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on alm_update_test_case? +

Register the HP ALM MCP Server MCP server in PolicyLayer and add a rule for alm_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 HP ALM MCP Server. Nothing to install.

What risk level is alm_update_test_case? +

alm_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 alm_update_test_case? +

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

Set action: deny in the PolicyLayer policy for alm_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 alm_update_test_case? +

alm_update_test_case is provided by the HP ALM MCP Server MCP server (uditmahaldar/opentext-alm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.