clear-session-notifications
Clear captured notifications for a session
This record as markdown: /tools/frontmcp/clear-session-notifications.md
What clear-session-notifications does on Frontmcp
AI agents call clear-session-notifications to permanently remove resources in Frontmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why clear-session-notifications is rated Critical
Clearing captured notifications removes data that cannot be recovered after the operation, making it a destructive action. The blast radius is medium because it affects session-scoped notification history rather than broader system data, but the loss is irreversible.
From the tool's definition "Clear captured notifications for a session" — the word 'clear' implies irreversible removal of stored notification data for a session.
Attacks that exploit this kind of access
The rule that runs clear-session-notifications safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear-session-notifications, this is the rule to start with:
clear-session-notifications is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every clear-session-notifications call is checked against it from then on.
Questions about clear-session-notifications
Clear captured notifications for a session. It is categorised as a Destructive tool in the Frontmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Front MCP server in PolicyLayer and add a rule for clear-session-notifications: 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 Frontmcp. Nothing to install.
clear-session-notifications 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 clear-session-notifications 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 clear-session-notifications. 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.
clear-session-notifications is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
Across the catalogue