get_handoff_status

Retrieve the current workspace handoff status, including active chain of receipts, blocked status, and any next safe action.

Server Chronicle MCP pypi:chronicle-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_handoff_status does on Chronicle MCP

AI agents call get_handoff_status to retrieve information from Chronicle MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_handoff_status needs a policy

This tool performs a read-only query of handoff state metadata. It retrieves status information without modifying, creating, executing, or deleting any data. The description explicitly indicates information retrieval with no mutations or external operations triggered. Severity is low because misuse would only expose existing state data, not enable harmful actions or data loss.

From the tool's definition Tool name 'get_handoff_status' and description 'Retrieve the current workspace handoff status' — uses passive retrieval verb 'Retrieve' to query state information (active chain of receipts, blocked status, next safe action) with no side effects.

Questions about get_handoff_status

What does the get_handoff_status tool do? +

Retrieve the current workspace handoff status, including active chain of receipts, blocked status, and any next safe action. It is categorised as a Read tool in the Chronicle MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_handoff_status? +

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

What risk level is get_handoff_status? +

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

Can I rate-limit get_handoff_status? +

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

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

get_handoff_status is provided by the Chronicle MCP server (pypi:chronicle-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.