heartbeat_protocol

Returns the canonical UnClick AI Seat heartbeat playbook. Call this first from scheduled heartbeat seats, then follow the returned versioned procedure exactly.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/heartbeat-protocol.md

WHAT IT DOES

What heartbeat_protocol does on UnClick

AI agents call heartbeat_protocol to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why heartbeat_protocol is rated Low

This tool queries and retrieves a heartbeat playbook configuration—a read-only retrieval operation. There are no side effects, data modifications, destructive actions, financial transactions, or code execution. The tool is instructional in nature (returning a procedure to follow) rather than operational.

From the tool's definition Returns the canonical UnClick AI Seat heartbeat playbook; described as retrieving a versioned procedure to follow, with no indication of modifying data or triggering external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs heartbeat_protocol safely

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

heartbeat_protocol Allowed

heartbeat_protocol is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "heartbeat_protocol": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about heartbeat_protocol

What does the heartbeat_protocol tool do? +

Returns the canonical UnClick AI Seat heartbeat playbook. Call this first from scheduled heartbeat seats, then follow the returned versioned procedure exactly. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on heartbeat_protocol? +

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

What risk level is heartbeat_protocol? +

heartbeat_protocol is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit heartbeat_protocol? +

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

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

heartbeat_protocol is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →