Start a new journaling session by clearing previous conversation log.
AI agents call start_new_session to permanently remove resources in MCP Journaling Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Starting a new session clears the previous conversation log, which constitutes irreversible destruction of existing data. Even though a 'new session' framing sounds innocuous, the operative action is clearing/deleting prior log data, which cannot be undone. This warrants a Destructive classification.
From the tool's definition 'clearing previous conversation log' — the act of clearing/wiping the prior conversation log is irreversible data removal
Documented attack patterns abuse exactly the kind of access start_new_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Journaling Server, and nothing reaches the server without passing your rules. This is the rule we recommend for start_new_session:
{
"version": "1",
"default": "deny",
"hide": [
"start_new_session"
]
}start_new_session disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Start a new journaling session by clearing previous conversation log. It is categorised as a Destructive tool in the MCP Journaling Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Journaling Server MCP server in PolicyLayer and add a rule for start_new_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 MCP Journaling Server. Nothing to install.
start_new_session is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the start_new_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.
Set action: deny in the PolicyLayer policy for start_new_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.
start_new_session is provided by the MCP Journaling Server MCP server (mtct/journaling-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Journaling Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 MCP Journaling Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.