alm_update_run_step · HP ALM MCP Server MCP: Risk & Policy

WHAT IT DOES

What alm_update_run_step does on HP ALM MCP Server

AI agents use alm_update_run_step 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_step needs a policy

This tool modifies test run step records within HP ALM's test execution workflow. While the description is empty (lowering confidence slightly), the naming pattern combined with sibling tools' context suggests it updates existing test execution state reversibly. This is a Write operation rather than Execute because it modifies structured QA workflow data rather than executing arbitrary operations.

From the tool's definition Tool name 'alm_update_run_step' indicates modification of test run step data within HP ALM. Related tools on the same server include 'alm_create_test_run', 'alm_checkin_test', and 'alm_checkout_test', which are all write/modify operations in a QA workflow…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

alm_update_run_step Rate-limited

alm_update_run_step 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_step": {
      "limits": [
        {
          "counter": "alm_update_run_step_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_step

What does the alm_update_run_step tool do? +

alm_update_run_step. 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_step? +

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

alm_update_run_step 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_step? +

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

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

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