manage_heartbeat

Enable or disable the heartbeat (periodic wake-up) for a digital twin / agent role.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/manage-heartbeat.md

WHAT IT DOES

What manage_heartbeat does on CoWork OS

AI agents use manage_heartbeat to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.

RISK

Why manage_heartbeat is rated Medium

This tool creates or modifies configuration state (enabling/disabling heartbeat functionality) reversibly without deleting data or executing arbitrary code. It affects the operational behavior of an agent but the change can be undone (re-enabled if disabled, vice versa).

From the tool's definition Tool description states 'Enable or disable the heartbeat (periodic wake-up) for a digital twin / agent role' — this modifies operational state of an agent/digital twin by toggling its periodic activation mechanism.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs manage_heartbeat safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For manage_heartbeat, this is the rule to start with:

manage_heartbeat Rate-limited

manage_heartbeat 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": {
    "manage_heartbeat": {
      "limits": [
        {
          "counter": "manage_heartbeat_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every manage_heartbeat call is checked against it from then on.

FAQ

Questions about manage_heartbeat

What does the manage_heartbeat tool do? +

Enable or disable the heartbeat (periodic wake-up) for a digital twin / agent role. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_heartbeat? +

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

What risk level is manage_heartbeat? +

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

Can I rate-limit manage_heartbeat? +

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

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

manage_heartbeat is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →