flares_presenceHeartbeat

Create or refresh a tenant-scoped presence session (POST /v1/flares/presence/heartbeat)

SERVERGenesis SOURCE@onesi/genesis-mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/onesi-genesis-mcp/flares-presenceheartbeat.md

WHAT IT DOES

What flares_presenceHeartbeat does on Genesis

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

Parameter	Type	Required	Description
`body`	object	Yes
`idempotency_key`	string	Yes	Stable key (required); reuse it to replay instead of acting twice

Parameters from the server's own tool schema.

RISK

Why flares_presenceHeartbeat is rated Medium

An AI agent can call flares_presenceHeartbeat faster than any human can review: one bad instruction and it creates or modifies resources in Genesis by the hundred, each call as confident as the last.

Risk signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs flares_presenceHeartbeat safely

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

flares_presenceHeartbeat Rate-limited

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

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about flares_presenceHeartbeat

What does the flares_presenceHeartbeat tool do? +

Create or refresh a tenant-scoped presence session (POST /v1/flares/presence/heartbeat). It is categorised as a Write tool in the Genesis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does flares_presenceHeartbeat accept? +

flares_presenceHeartbeat accepts 2 parameters: body, idempotency_key. Required: body, idempotency_key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on flares_presenceHeartbeat? +

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

What risk level is flares_presenceHeartbeat? +

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

Can I rate-limit flares_presenceHeartbeat? +

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

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

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

KEEP EXPLORING

More on Genesis, and thousands of servers like it.

This server

All 1127 Genesis tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →