acknowledge_health_alarm · Morpheus MCP Server MCP

WHAT IT DOES

What acknowledge_health_alarm does on Morpheus MCP Server

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

WHY IT NEEDS A POLICY

Why acknowledge_health_alarm needs a policy

Acknowledging an alarm is a state change (marking it as seen/acknowledged) which is a reversible write operation. It does not delete data, execute code, or have financial implications. The blast radius is low since misuse only affects alarm tracking state.

From the tool's definition Acknowledge a specific health alarm by ID

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

acknowledge_health_alarm Rate-limited

acknowledge_health_alarm 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": {
    "acknowledge_health_alarm": {
      "limits": [
        {
          "counter": "acknowledge_health_alarm_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 Morpheus MCP Server, so you can run agents against it safely.

FAQ

Questions about acknowledge_health_alarm

What does the acknowledge_health_alarm tool do? +

Acknowledge a specific health alarm by ID. It is categorised as a Write tool in the Morpheus 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 acknowledge_health_alarm? +

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

What risk level is acknowledge_health_alarm? +

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

Can I rate-limit acknowledge_health_alarm? +

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

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

acknowledge_health_alarm is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.