Store a journal entry with auto-extracted mood and energy.
AI agents use add_journal_entry 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.
This tool creates or writes new journal entry data to the user's local system with auto-extracted metadata (mood, energy). The operation is reversible (entries can be edited or deleted later). It has no destructive, execute, or financial characteristics. The low severity reflects that misuse would only create unwanted journal entries in a personal knowledge base, with minimal blast radius.
From the tool's definition Tool name includes 'add' and description states 'Store a journal entry', indicating creation of new data with reversible effects.
Attacks that exploit this kind of access
Store a journal entry with auto-extracted mood and energy. 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 add_journal_entry: 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.
add_journal_entry 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 add_journal_entry 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 add_journal_entry. 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.
add_journal_entry 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 →