generate_handoff_brief
AI agents use generate_handoff_brief to create or update resources in Metis Public Health — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metis Public Health environment.
The tool appears to generate and store a handoff brief—a document or data structure created for agent-to-agent communication within Metis's 34-specialist agent architecture. This is a Write operation (creates reversible data). Severity is medium because misuse could create misleading or confidential documentation, but the local-first architecture limits blast radius.
From the tool's definition Tool name 'generate_handoff_brief' suggests creating documentation or a structured summary artifact for transfer between agents or contexts.
Attacks that exploit this kind of access
generate_handoff_brief. It is categorised as a Write tool in the Metis Public Health MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for generate_handoff_brief: 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 Metis Public Health. Nothing to install.
generate_handoff_brief 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 generate_handoff_brief 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 generate_handoff_brief. 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.
generate_handoff_brief is provided by the Metis Public Health MCP server (sveritg/metis_ph). 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 →