alm_update_run_status · HP ALM MCP Server MCP: Risk & Policy

WHAT IT DOES

What alm_update_run_status does on HP ALM MCP Server

AI agents use alm_update_run_status 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_run_status needs a policy

This tool creates or modifies data (test run status) in a reversible manner. It does not delete, destroy, or permanently alter records (Destructive), does not execute arbitrary code (Execute), and does not involve financial transactions (Financial). Status updates in QA systems are write operations that can be undone or corrected.

From the tool's definition 'Update the overall pass/fail status of a test run' — modifies test run status, a QA workflow data state that is reversible and non-destructive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

alm_update_run_status Rate-limited

alm_update_run_status 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_run_status": {
      "limits": [
        {
          "counter": "alm_update_run_status_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_run_status

What does the alm_update_run_status tool do? +

Update the overall pass/fail status of a test run. 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_run_status? +

Register the HP ALM MCP Server MCP server in PolicyLayer and add a rule for alm_update_run_status: 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_run_status? +

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

Can I rate-limit alm_update_run_status? +

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

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

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