alm_checkout_test · HP ALM MCP Server MCP: Risk & Policy

WHAT IT DOES

What alm_checkout_test does on HP ALM MCP Server

AI agents use alm_checkout_test 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_checkout_test needs a policy

This tool acquires a lock on a test case to enable subsequent edits to its properties and design steps. While checkout itself is a control operation (acquiring write access), the stated purpose is to facilitate Write operations (editing fields and design steps). The effects are reversible—changes can be undone, updates can be reverted, and the checkout lock can be released.

From the tool's definition 'Check out a test case so its fields and design steps can be edited' — the tool explicitly enables editing of test case fields and design steps, which are reversible modifications to data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

alm_checkout_test Rate-limited

alm_checkout_test 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_checkout_test": {
      "limits": [
        {
          "counter": "alm_checkout_test_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_checkout_test

What does the alm_checkout_test tool do? +

Check out a test case so its fields and design steps can be edited. 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_checkout_test? +

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

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

Can I rate-limit alm_checkout_test? +

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

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

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