end_work_session | PolicyLayer

WHAT IT DOES

What end_work_session does on Studio Catharsis Universal Project Coordinator MCP

AI agents use end_work_session to create or update resources in Studio Catharsis Universal Project Coordinator MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Studio Catharsis Universal Project Coordinator MCP environment.

WHY IT NEEDS A POLICY

Why end_work_session needs a policy

end_work_session creates or records a new work session closure record with summary data, which is a reversible data modification (Write category). It does not execute arbitrary code, delete data irreversibly, or move money. Severity is medium because misuse could pollute project records with false summaries or context, creating confusion for other team members, but the effects are reviewable and correctable.

From the tool's definition Tool description states 'End a work session with summary and context' and mentions noting 'Git-pushed changes', indicating it records/commits session state and work summaries.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

end_work_session Rate-limited

end_work_session 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": {
    "end_work_session": {
      "limits": [
        {
          "counter": "end_work_session_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 Studio Catharsis Universal Project Coordinator MCP, so you can run agents against it safely.

FAQ

Questions about end_work_session

What does the end_work_session tool do? +

End a work session with summary and context. Git-pushed changes should be noted. It is categorised as a Write tool in the Studio Catharsis Universal Project Coordinator MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on end_work_session? +

Register the Studio Catharsis Universal Project Coordinator MCP server in PolicyLayer and add a rule for end_work_session: 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 Studio Catharsis Universal Project Coordinator MCP. Nothing to install.

What risk level is end_work_session? +

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

Can I rate-limit end_work_session? +

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

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

end_work_session is provided by the Studio Catharsis Universal Project Coordinator MCP server (studio-catharsis-creative-lab/project_com_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.