commit_session_decisions · Metis Public Health MCP

WHAT IT DOES

What commit_session_decisions does on Metis Public Health

AI agents use commit_session_decisions 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 commit_session_decisions needs a policy

The verb 'commit' combined with 'session_decisions' suggests persisting mutable state (Write category). It is reversible (unlike Destructive), does not execute arbitrary code (unlike Execute), and does not move money (not Financial). Severity is medium because committing decisions could affect subsequent AI reasoning if decisions are incorrect or malicious, but impact is local-first per server description.

From the tool's definition Tool name 'commit_session_decisions' indicates persisting or finalizing decisions made during a session, which modifies stored state. Description is empty, reducing confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

commit_session_decisions Rate-limited

commit_session_decisions 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": {
    "commit_session_decisions": {
      "limits": [
        {
          "counter": "commit_session_decisions_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 commit_session_decisions

What does the commit_session_decisions tool do? +

commit_session_decisions. 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 commit_session_decisions? +

Register the Metis Public Health MCP server in PolicyLayer and add a rule for commit_session_decisions: 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 commit_session_decisions? +

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

Can I rate-limit commit_session_decisions? +

Yes. Add a rate_limit block to the commit_session_decisions 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 commit_session_decisions completely? +

Set action: deny in the PolicyLayer policy for commit_session_decisions. 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 commit_session_decisions? +

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