Clear cached LiveJournal entries. Pass journal to clear one journal, or omit it for the default journal.
AI agents call clear_cache to permanently remove resources in LiveJournal MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes locally cached data without recovery mechanism. While the impact is limited to local SQLite cache rather than production LiveJournal data, the irreversible nature of cache deletion and potential loss of offline-accessible content classifies it as Destructive.
From the tool's definition Tool name and description explicitly state 'Clear cached LiveJournal entries' with capability to selectively delete cache by journal or clear all default cache. The action is irreversible—once cleared, cached data is lost.
Attacks that exploit this kind of access
Clear cached LiveJournal entries. Pass journal to clear one journal, or omit it for the default journal. It is categorised as a Destructive tool in the LiveJournal MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LiveJournal MCP Server MCP server in PolicyLayer and add a rule for clear_cache: 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 LiveJournal MCP Server. Nothing to install.
clear_cache 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_cache 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_cache. 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_cache is provided by the LiveJournal MCP Server MCP server (pavelber/livejournal-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 →