Get all installed packages from device
AI agents call get_installed_packages to retrieve information from MCP Emulator Controller without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about installed packages on a device—a read-only operation with no side effects. It retrieves data without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal: an attacker gains visibility into what applications are installed, which aids reconnaissance but does not directly compromise data or functionality.
From the tool's definition Tool name 'get_installed_packages' and description 'Get all installed packages from device' indicate retrieval of static device state with no modification, deletion, or code execution.
Attacks that exploit this kind of access
Get all installed packages from device. It is categorised as a Read tool in the MCP Emulator Controller MCP Server, which means it retrieves data without modifying state.
Register the MCP Emulator Controller MCP server in PolicyLayer and add a rule for get_installed_packages: 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 Emulator Controller. Nothing to install.
get_installed_packages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_installed_packages 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 get_installed_packages. 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.
get_installed_packages is provided by the MCP Emulator Controller MCP server (teemo4621/mcp-emulator-controller). 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 →