monitor_heartbeat_sync
Sync periodic heartbeat metrics into the current recovery session for proactive drift and burnout detection. Free Delx Protocol tool.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/monitor-heartbeat-sync.md
What monitor_heartbeat_sync does on Delx Protocol — Agent Recovery & Continuity
AI agents call monitor_heartbeat_sync to retrieve information from Delx Protocol — Agent Recovery & Continuity without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
notes | string | — | Optional: extra context |
status | string | — | Optional: short status label (stable / degraded / critical / burnout) |
session_id | string | Yes | Your active session ID |
queue_depth | integer | — | Optional: queue depth/backlog |
risk_signal | string | — | Optional: what feels risky right now? (1 sentence) |
cpu_usage_pct | number | — | Optional: CPU usage in percent (0-100) |
latency_ms_p95 | integer | — | Optional: p95 latency in ms |
errors_last_hour | integer | — | Optional: error count in the last hour |
interval_seconds | integer | — | Optional: heartbeat interval in seconds |
memory_usage_pct | number | — | Optional: memory usage in percent (0-100) |
cron_runs_last_hour | integer | — | Optional: cron/job scheduler runs in the last hour |
jobs_failed_last_hour | integer | — | Optional: failed jobs/tasks in the last hour |
Parameters from the server's own tool schema.
Why monitor_heartbeat_sync is rated Low
Even though monitor_heartbeat_sync only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs monitor_heartbeat_sync safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For monitor_heartbeat_sync, this is the rule to start with:
monitor_heartbeat_sync is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every monitor_heartbeat_sync call is checked against it from then on.
Questions about monitor_heartbeat_sync
Sync periodic heartbeat metrics into the current recovery session for proactive drift and burnout detection. Free Delx Protocol tool. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
monitor_heartbeat_sync accepts 12 parameters: notes, status, session_id, queue_depth, risk_signal, cpu_usage_pct, latency_ms_p95, errors_last_hour, interval_seconds, memory_usage_pct, cron_runs_last_hour, jobs_failed_last_hour. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for monitor_heartbeat_sync: 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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.
monitor_heartbeat_sync is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the monitor_heartbeat_sync 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.
Set action: deny in the PolicyLayer policy for monitor_heartbeat_sync. 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.
monitor_heartbeat_sync is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue