This record as markdown: /tools/delimit/delimit-heartbeat-check.md
What delimit_heartbeat_check does on Delimit
AI agents call delimit_heartbeat_check to retrieve information from Delimit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why delimit_heartbeat_check is rated Low
A heartbeat check is typically a non-destructive operation that verifies if a service or agent is alive and responsive. This is a read-only diagnostic query with no side effects. Confidence is moderate (0.7) due to the empty description; if the tool actually modifies state or triggers actions, it could be Execute, but the name strongly suggests passive monitoring.
From the tool's definition Tool name 'delimit_heartbeat_check' suggests a health/status check operation. Description is empty, limiting direct evidence, but naming pattern aligns with monitoring/querying tool status rather than data modification or execution.
Attacks that exploit this kind of access
The rule that runs delimit_heartbeat_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delimit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delimit_heartbeat_check, this is the rule to start with:
delimit_heartbeat_check 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 Delimit, apply this rule, and every delimit_heartbeat_check call is checked against it from then on.
Questions about delimit_heartbeat_check
delimit_heartbeat_check is a read tool on the Delimit MCP server. It is categorised as a Read tool in the Delimit MCP Server, which means it retrieves data without modifying state.
Register the Delimit MCP server in PolicyLayer and add a rule for delimit_heartbeat_check: 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 Delimit. Nothing to install.
delimit_heartbeat_check 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 delimit_heartbeat_check 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 delimit_heartbeat_check. 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.
delimit_heartbeat_check is provided by the Delimit MCP server (delimit-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delimit, and thousands of servers like it.
This server
Across the catalogue