# app_status

Build/run status of a container app deployed via publish_site with a Dockerfile. Poll until status is live or failed.

Agent View of the PolicyLayer registry record for `app_status`. HTML page: https://policylayer.com/tools/ai-dataecho-mcp/app-status

## Facts

- Tool: `app_status`
- Server: Mcp (`https://dataecho.ai/mcp`) — https://policylayer.com/tools/ai-dataecho-mcp.md
- Homepage: https://github.com/mohocp/dataecho
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `logs` | boolean | no | Include build logs |
| `slug` | string | yes | Site slug |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "app_status",
    "arguments": {
      "slug": "<slug>"
    }
  }
}
```

## Why app_status is rated Low

app_status is a read-only operation that retrieves status information about an already-deployed container. It has no side effects, does not execute code or trigger deployments, and does not modify any data. The action is purely observational—checking the state of an existing resource. Severity is low because misuse would only reveal status information without enabling harmful actions.

From the tool's own definition: "Tool description states 'Poll until status is `live` or `failed`', indicating it queries and retrieves the current build/run status of a deployed container app without modifying or executing anything."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "app_status": {}
  }
}
```

## Other tools on Mcp (25)

- `delete_site` — Destructive — https://policylayer.com/tools/ai-dataecho-mcp/delete-site.md
- `delete_variable` — Destructive — https://policylayer.com/tools/ai-dataecho-mcp/delete-variable.md
- `drive_delete_file` — Destructive — https://policylayer.com/tools/ai-dataecho-mcp/drive-delete-file.md
- `drive_revoke_token` — Destructive — https://policylayer.com/tools/ai-dataecho-mcp/drive-revoke-token.md
- `drive_history` — Read — https://policylayer.com/tools/ai-dataecho-mcp/drive-history.md
- `drive_list_files` — Read — https://policylayer.com/tools/ai-dataecho-mcp/drive-list-files.md
- `drive_read_file` — Read — https://policylayer.com/tools/ai-dataecho-mcp/drive-read-file.md
- `drive_tokens` — Read — https://policylayer.com/tools/ai-dataecho-mcp/drive-tokens.md
- `get_site` — Read — https://policylayer.com/tools/ai-dataecho-mcp/get-site.md
- `list_drives` — Read — https://policylayer.com/tools/ai-dataecho-mcp/list-drives.md
- `list_sites` — Read — https://policylayer.com/tools/ai-dataecho-mcp/list-sites.md
- `list_variables` — Read — https://policylayer.com/tools/ai-dataecho-mcp/list-variables.md
- `platform_info` — Read — https://policylayer.com/tools/ai-dataecho-mcp/platform-info.md
- `search_sites` — Read — https://policylayer.com/tools/ai-dataecho-mcp/search-sites.md
- `verify_login_code` — Read — https://policylayer.com/tools/ai-dataecho-mcp/verify-login-code.md
- `claim_site` — Write — https://policylayer.com/tools/ai-dataecho-mcp/claim-site.md
- `create_drive` — Write — https://policylayer.com/tools/ai-dataecho-mcp/create-drive.md
- `drive_move_file` — Write — https://policylayer.com/tools/ai-dataecho-mcp/drive-move-file.md
- `drive_restore` — Write — https://policylayer.com/tools/ai-dataecho-mcp/drive-restore.md
- `drive_share` — Write — https://policylayer.com/tools/ai-dataecho-mcp/drive-share.md
- `drive_write_file` — Write — https://policylayer.com/tools/ai-dataecho-mcp/drive-write-file.md
- `publish_site` — Write — https://policylayer.com/tools/ai-dataecho-mcp/publish-site.md
- `request_login_code` — Write — https://policylayer.com/tools/ai-dataecho-mcp/request-login-code.md
- `set_variable` — Write — https://policylayer.com/tools/ai-dataecho-mcp/set-variable.md
- `update_site_metadata` — Write — https://policylayer.com/tools/ai-dataecho-mcp/update-site-metadata.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=ai-dataecho-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ai-dataecho-mcp