Flush temporary/abandoned uploads.
AI agents call wiki_assets_flush_temp to permanently remove resources in Mcp Wikijs Mv — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
'Flush' implies permanent deletion or purging of temporary upload data. While the targets are 'temporary/abandoned' uploads, the operation is irreversible — once flushed, those assets cannot be recovered. This matches the Destructive category. Severity is high because a misconfigured or malicious invocation could purge uploads that were not yet fully processed or confirmed, causing data loss.
From the tool's definition Flush temporary/abandoned uploads
Attacks that exploit this kind of access
Flush temporary/abandoned uploads. It is categorised as a Destructive tool in the Mcp Wikijs Mv MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Wikijs Mv MCP server in PolicyLayer and add a rule for wiki_assets_flush_temp: 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 Mcp Wikijs Mv. Nothing to install.
wiki_assets_flush_temp 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 wiki_assets_flush_temp 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 wiki_assets_flush_temp. 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.
wiki_assets_flush_temp is provided by the Mcp Wikijs Mv MCP server (janschachtschabel/mcp-for-wiki-js). 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 →