pine_session_delete
Delete a Pine AI session.
This record as markdown: /tools/19pine-ai-pine-mcp-server/pine-session-delete.md
What pine_session_delete does on Pine Assistant MCP Server
AI agents call pine_session_delete to permanently remove resources in Pine Assistant MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why pine_session_delete is rated Critical
This tool permanently deletes Pine AI session data, which cannot be undone. Session deletion is a destructive action that removes records and cannot be reversed through normal means.
From the tool's definition Tool name is 'pine_session_delete' and description states 'Delete a Pine AI session.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs pine_session_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pine Assistant MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pine_session_delete, this is the rule to start with:
pine_session_delete 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 Pine Assistant MCP Server, apply this rule, and every pine_session_delete call is checked against it from then on.
Questions about pine_session_delete
Delete a Pine AI session. It is categorised as a Destructive tool in the Pine Assistant MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pine Assistant MCP Server MCP server in PolicyLayer and add a rule for pine_session_delete: 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 Pine Assistant MCP Server. Nothing to install.
pine_session_delete 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 pine_session_delete 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 pine_session_delete. 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.
pine_session_delete is provided by the Pine Assistant MCP Server MCP server (19pine-ai/pine-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pine Assistant MCP Server, and thousands of servers like it.
Across the catalogue