clear-session-notifications

Clear captured notifications for a session

SERVERFrontmcp SOURCEagentfront/frontmcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about clear-session-notifications

What does the clear-session-notifications tool do? +

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.

How do I enforce a policy on clear-session-notifications? +

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.

What risk level is clear-session-notifications? +

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.

Can I rate-limit clear-session-notifications? +

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.

How do I block clear-session-notifications completely? +

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.

What MCP server provides clear-session-notifications? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Front's. Pull the full record:

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.