Extend the lease on a claimed task so it does not expire while work is in progress.
AI agents use heartbeat_lease to create or update resources in State Trace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your State Trace environment.
The tool modifies the state of a task lease (extending its expiry time), which is a reversible write operation with minimal blast radius — it simply prevents a task from timing out and does not delete, execute code, or involve financial transactions.
From the tool's definition Extend the lease on a claimed task so it does not expire while work is in progress
Attacks that exploit this kind of access
Extend the lease on a claimed task so it does not expire while work is in progress. It is categorised as a Write tool in the State Trace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the State Trace MCP server in PolicyLayer and add a rule for heartbeat_lease: 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 State Trace. Nothing to install.
heartbeat_lease is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the heartbeat_lease 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 heartbeat_lease. 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.
heartbeat_lease is provided by the State Trace MCP server (agent-pattern-labs/state-trace). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →