Clean FlowDroid workspace directory
AI agents call clean_flowdroid_workspace to permanently remove resources in APK Security Guard MCP Suite — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cleaning a workspace directory typically means deleting its contents permanently. While the blast radius is limited to the FlowDroid workspace (not production data), the action is irreversible and constitutes destructive behavior. Severity is medium because it only affects analysis/workspace files, not core application or user data.
From the tool's definition Clean FlowDroid workspace directory — 'clean' implies irreversible deletion or removal of workspace files/directories
Attacks that exploit this kind of access
Clean FlowDroid workspace directory. It is categorised as a Destructive tool in the APK Security Guard MCP Suite MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the APK Security Guard MCP Suite MCP server in PolicyLayer and add a rule for clean_flowdroid_workspace: 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 APK Security Guard MCP Suite. Nothing to install.
clean_flowdroid_workspace 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 clean_flowdroid_workspace 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 clean_flowdroid_workspace. 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.
clean_flowdroid_workspace is provided by the APK Security Guard MCP Suite MCP server (zmbcen/apk-security-guard-mcp-suite). 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 →