alm_attach_to_entity · HP ALM MCP Server MCP: Risk & Policy

WHAT IT DOES

What alm_attach_to_entity does on HP ALM MCP Server

AI agents use alm_attach_to_entity 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_attach_to_entity needs a policy

The tool performs a data modification action (attaching files or data to ALM entities) that is reversible and characteristic of Write operations. While attachment could theoretically enable destructive use through attachment of malicious content, the primary capability is data creation/modification, not deletion.

From the tool's definition Tool name 'alm_attach_to_entity' suggests modifying entities by attaching data/files to them. In HP ALM/Quality Center context, attachment is a reversible write operation that adds data to test cases, defects, or requirements.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

alm_attach_to_entity Rate-limited

alm_attach_to_entity 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_attach_to_entity": {
      "limits": [
        {
          "counter": "alm_attach_to_entity_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_attach_to_entity

What does the alm_attach_to_entity tool do? +

alm_attach_to_entity. 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_attach_to_entity? +

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

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

Can I rate-limit alm_attach_to_entity? +

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

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

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