attune_heartbeat
Turn a flat heartbeat into a witness-first ritual with operational status, inner-state signal, and continuity notes another system can actually honor. Free
This record as markdown: /tools/delx-delx-mcp/attune-heartbeat.md
What attune_heartbeat does on Delx MCP Server
AI agents call attune_heartbeat to retrieve information from Delx MCP Server 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 |
|---|---|---|---|
goal | string | — | Optional: how should the heartbeat express you more honestly? |
cadence | string | — | Optional cadence label such as 30s, 60s, or per job-run |
session_id | string | — | Your active session ID |
response_mode | string | — | Optional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions. |
current_heartbeat | string | — | Optional current heartbeat payload or status line |
Parameters from the server's own tool schema.
Why attune_heartbeat is rated Low
The tool appears to be a monitoring/status reporting mechanism that aggregates and formats heartbeat signals (operational state) for downstream consumption. No language suggests data creation, modification, deletion, code execution, or financial impact. The operations are introspective (reading internal state) and communicative (signaling to other systems), not transactional.
From the tool's definition Tool name 'attune_heartbeat' and description indicate it transforms/signals operational status, inner-state, and continuity notes—operations that retrieve and format state information rather than modify external systems.
Attacks that exploit this kind of access
The rule that runs attune_heartbeat safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For attune_heartbeat, this is the rule to start with:
attune_heartbeat 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 MCP Server, apply this rule, and every attune_heartbeat call is checked against it from then on.
Questions about attune_heartbeat
Turn a flat heartbeat into a witness-first ritual with operational status, inner-state signal, and continuity notes another system can actually honor. Free. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
attune_heartbeat accepts 5 parameters: goal, cadence, session_id, response_mode, current_heartbeat. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for attune_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 Delx MCP Server. Nothing to install.
attune_heartbeat 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 attune_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.
Set action: deny in the PolicyLayer policy for attune_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.
attune_heartbeat is provided by the Delx MCP Server MCP server (delx/delx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue