save_daily_brief
AI agents use save_daily_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 name strongly suggests it creates or stores a daily brief—a reversible Write operation. No description is provided, which lowers confidence moderately. Given the context of Metis as a local-first research companion and the pattern of sibling tools (add_glossary_term, add_journal_entry, add_memory_entry), saving a brief is consistent with creating or appending local data.
From the tool's definition Tool name 'save_daily_brief' indicates writing/storing a daily summary or report. The verb 'save' suggests creating or persisting data to the local system.
Attacks that exploit this kind of access
save_daily_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 save_daily_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.
save_daily_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 save_daily_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 save_daily_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.
save_daily_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 →