save_session_event · Metis Public Health MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why save_session_event needs a policy

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

Recommended rule Ready

Verdict

save_session_event Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_session_event": {
      "limits": [
        {
          "counter": "save_session_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Metis Public Health, so you can run agents against it safely.

FAQ

Questions about save_session_event

What does the save_session_event tool do? +

save_session_event. 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.

How do I enforce a policy on save_session_event? +

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.

What risk level is save_session_event? +

save_session_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_session_event? +

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.

How do I block save_session_event completely? +

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.

What MCP server provides save_session_event? +

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.

// THE FULL RECORD

save_session_event is one line of Metis Public Health's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →