Clear current analysis session and cached data
AI agents call clear_session to permanently remove resources in Spark EventLog MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While the data deletion is scoped to the current analysis session rather than permanent external data, clearing cached data and session state is an irreversible operation that destroys intermediate analysis work and cached computation results. This fits Destructive because the action cannot be undone and results in data loss.
From the tool's definition The tool performs 'clear current analysis session and cached data' which irreversibly removes session state and cached analysis results. This cannot be undone.
Attacks that exploit this kind of access
Clear current analysis session and cached data. It is categorised as a Destructive tool in the Spark EventLog MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Spark EventLog MCP Server MCP server in PolicyLayer and add a rule for clear_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 Spark EventLog MCP Server. Nothing to install.
clear_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 clear_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 clear_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.
clear_session is provided by the Spark EventLog MCP Server MCP server (yhyyz/spark-eventlog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →