create_heartbeat · Pingera MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_heartbeat does on Pingera MCP Server

AI agents use create_heartbeat to create or update resources in Pingera MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pingera MCP Server environment.

WHY IT NEEDS A POLICY

Why create_heartbeat needs a policy

Heartbeat creation in a monitoring service creates new monitoring configuration or status records, which is a reversible write operation. This is a side-effect operation that modifies the monitoring system state but is not irreversible (heartbeats can typically be deleted or updated), does not execute arbitrary code, and does not involve financial transactions.

From the tool's definition Tool name 'create_heartbeat' indicates creation of a new heartbeat monitoring entity. The prefix 'create_' combined with the sibling tools on this server (create_alert, create_check, create_component, etc.) establishes a clear Write pattern.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_heartbeat Rate-limited

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pingera MCP Server, so you can run agents against it safely.

FAQ

Questions about create_heartbeat

What does the create_heartbeat tool do? +

create_heartbeat. It is categorised as a Write tool in the Pingera MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_heartbeat? +

Register the Pingera MCP Server MCP server in PolicyLayer and add a rule for create_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 Pingera MCP Server. Nothing to install.

What risk level is create_heartbeat? +

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

Can I rate-limit create_heartbeat? +

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

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

create_heartbeat is provided by the Pingera MCP Server MCP server (pingera/pingera-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.