save_session_event
A write tool on the Metis Public Health MCP server.
This record as markdown: /tools/sveritg-metis-ph/save-session-event.md
What save_session_event does on Metis Public Health
AI agents use save_session_event 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.
Why save_session_event is rated Medium
The tool saves session events, which modifies persistent state by recording user interactions or system state. This is a Write operation (reversible modification of data) rather than Read (no retrieval indicated), Execute (no external code/commands), or Destructive (not irreversible deletion).
From the tool's definition Tool name 'save_session_event' indicates persistence of session data; the verb 'save' denotes creating or modifying records. No description provided to refine classification.
Attacks that exploit this kind of access
The rule that runs save_session_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_session_event, this is the rule to start with:
save_session_event stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every save_session_event call is checked against it from then on.
Questions about save_session_event
save_session_event is a write tool on the Metis Public Health MCP server. 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_session_event: 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_session_event 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_session_event 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_session_event. 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_session_event 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.
More on Metis Public Health, and thousands of servers like it.
This server
Across the catalogue