is_app_running

Check whether an application is currently running. Returns process details if found.

SERVERIconnect SOURCEiconnect-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/is-app-running.md

WHAT IT DOES

What is_app_running does on Iconnect

AI agents call is_app_running to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why is_app_running is rated Low

This is a straightforward query tool that retrieves the running status and process details of an application. It has no side effects, does not modify system state, and does not execute arbitrary code or commands. It is purely informational and falls squarely within the Read category.

From the tool's definition Tool name and description indicate retrieval of process state: 'Check whether an application is currently running. Returns process details if found.' No modification, deletion, or execution of external operations occurs.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs is_app_running safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, 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 Allowed

is_app_running is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "is_app_running": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every is_app_running call is checked against it from then on.

FAQ

Questions about is_app_running

What does the is_app_running tool do? +

Check whether an application is currently running. Returns process details if found. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on is_app_running? +

Register the Iconnect 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 Iconnect. Nothing to install.

What risk level is is_app_running? +

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

Can I rate-limit is_app_running? +

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.

How do I block is_app_running completely? +

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.

What MCP server provides is_app_running? +

is_app_running is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →