find_leak_components_source

Find exported components without permissions and get their source code path.

Server APK Security Guard MCP Suite zmbcen/apk-security-guard-mcp-suite
Category Read
Risk class Low
Parameters 00 required

What find_leak_components_source does on APK Security Guard MCP Suite

AI agents call find_leak_components_source to retrieve information from APK Security Guard MCP Suite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why find_leak_components_source needs a policy

This is a pure information-retrieval tool used for security scanning. It analyzes APK structure to identify potential vulnerabilities (exported components lacking permission checks) and returns data about their locations. No code execution, modification, deletion, or external effects occur.

From the tool's definition Tool performs static analysis queries to 'Find exported components without permissions and get their source code path'—it retrieves and returns information about security properties and code locations without modifying or executing anything.

Questions about find_leak_components_source

What does the find_leak_components_source tool do? +

Find exported components without permissions and get their source code path. It is categorised as a Read tool in the APK Security Guard MCP Suite MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_leak_components_source? +

Register the APK Security Guard MCP Suite MCP server in PolicyLayer and add a rule for find_leak_components_source: 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.

What risk level is find_leak_components_source? +

find_leak_components_source is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_leak_components_source? +

Yes. Add a rate_limit block to the find_leak_components_source 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.

How do I block find_leak_components_source completely? +

Set action: deny in the PolicyLayer policy for find_leak_components_source. 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.

What MCP server provides find_leak_components_source? +

find_leak_components_source 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.