Run FlowDroid taint analysis on an APK
AI agents invoke run_flowdroid_analysis to trigger actions in APK Security Guard MCP Suite. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an external specialized analysis program (FlowDroid) with potentially complex side effects depending on the APK provided. While the primary output is analysis results (read-like), the action itself invokes external code execution on user-supplied APK files.
From the tool's definition Tool description states 'Run FlowDroid taint analysis on an APK' — the verb 'Run' indicates execution of an external analysis tool.
Attacks that exploit this kind of access
Run FlowDroid taint analysis on an APK. It is categorised as a Execute tool in the APK Security Guard MCP Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the APK Security Guard MCP Suite MCP server in PolicyLayer and add a rule for run_flowdroid_analysis: 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.
run_flowdroid_analysis is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_flowdroid_analysis 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 run_flowdroid_analysis. 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.
run_flowdroid_analysis 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 →