Clear all temporal memory (requires confirmation for safety).
AI agents call clear_temporal_memory to permanently remove resources in KafkaIQ — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes temporal memory records, which cannot be undone. While the confirmation requirement provides some mitigation, the action itself is destructive in nature—it erases historical data used for trend detection and monitoring.
From the tool's definition Tool name is 'clear_temporal_memory' and description states 'Clear all temporal memory (requires confirmation for safety)'. The verb 'clear' combined with 'all temporal memory' indicates irreversible deletion of historical state data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all temporal memory (requires confirmation for safety). It is categorised as a Destructive tool in the KafkaIQ MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the KafkaIQ MCP server in PolicyLayer and add a rule for clear_temporal_memory: 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 KafkaIQ. Nothing to install.
clear_temporal_memory 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_temporal_memory 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_temporal_memory. 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_temporal_memory is provided by the KafkaIQ MCP server (ojhaayush03/kafka_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 →