Check application installation and running status
AI agents call check_app_status 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 performs a read-only query to determine if an application is installed and whether it is currently running on the emulated device. It retrieves information but produces no side effects, modifications, or state changes. This is a low-severity Read action—misuse would only leak information about what apps are present or active, not compromise system integrity or cause irreversible changes.
From the tool's definition Tool name 'check_app_status' and description 'Check application installation and running status' indicate a query operation that retrieves state information without modifying anything.
Attacks that exploit this kind of access
Check application installation and running status. 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 check_app_status: 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.
check_app_status 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 check_app_status 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 check_app_status. 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.
check_app_status 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.
check_app_status is one line of MCP Emulator Controller's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →