is_app_running
Check whether an application is currently running. Returns process details if found.
This record as markdown: /tools/heznpc-airmcp/is-app-running.md
What is_app_running does on AirMCP
AI agents call is_app_running to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why is_app_running is rated Low
This is a pure information retrieval tool that queries the system for the running state of applications and returns process metadata. It has no side effects, cannot modify system state, and poses minimal security risk. The only minor concern is that process information could reveal system configuration, but this is typically already accessible to any user on the machine. Classified as Read with low severity.
From the tool's definition Tool name 'is_app_running' and description 'Check whether an application is currently running. Returns process details if found.' indicate a query operation that retrieves process status information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs is_app_running safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For is_app_running, this is the rule to start with:
is_app_running is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every is_app_running call is checked against it from then on.
Questions about is_app_running
Check whether an application is currently running. Returns process details if found. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air MCP server in PolicyLayer and add a rule for is_app_running: 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 AirMCP. Nothing to install.
is_app_running 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 is_app_running 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 is_app_running. 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.
is_app_running is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue