# abs_zalo_status

Bridge/account safety status: connected?, READ_ONLY_SOURCE, destination, corpus counts.

Agent View of the PolicyLayer registry record for `abs_zalo_status`. HTML page: https://policylayer.com/tools/abs-zalo-bot/abs-zalo-status

## Facts

- Tool: `abs_zalo_status`
- Server: Abs Zalo Bot (`abs-zalo-bot`) — https://policylayer.com/tools/abs-zalo-bot.md
- Install: `npx -y abs-zalo-bot`
- Homepage: git+https://github.com/teddiesloco/abs-zalo-bot.git
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "abs_zalo_status",
    "arguments": {}
  }
}
```

## Why abs_zalo_status is rated Low

Even though abs_zalo_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call abs_zalo_status to retrieve information from Abs Zalo Bot 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 Abs Zalo Bot:

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

## Other tools on Abs Zalo Bot (42)

- `abs_zalo_block_group_member` — Destructive — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-block-group-member.md
- `abs_zalo_kick_member` — Destructive — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-kick-member.md
- `abs_zalo_remove_deputy` — Destructive — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-remove-deputy.md
- `abs_zalo_undo_message` — Destructive — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-undo-message.md
- `abs_zalo_personal_action` — Execute — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-personal-action.md
- `abs_zalo_transfer_owner` — Financial — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-transfer-owner.md
- `abs_zalo_capability_packs` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-capability-packs.md
- `abs_zalo_change_group_avatar` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-change-group-avatar.md
- `abs_zalo_corpus_summary` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-corpus-summary.md
- `abs_zalo_find_user` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-find-user.md
- `abs_zalo_get_group_info` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-get-group-info.md
- `abs_zalo_get_group_link` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-get-group-link.md
- `abs_zalo_get_group_link_info` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-get-group-link-info.md
- `abs_zalo_get_pending_members` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-get-pending-members.md
- `abs_zalo_get_sticker_detail` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-get-sticker-detail.md
- `abs_zalo_get_user_info` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-get-user-info.md
- `abs_zalo_group_members` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-group-members.md
- `abs_zalo_history_range` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-history-range.md
- `abs_zalo_join_group_link` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-join-group-link.md
- `abs_zalo_list_all_groups` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-list-all-groups.md
- `abs_zalo_list_friends` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-list-friends.md
- `abs_zalo_list_groups` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-list-groups.md
- `abs_zalo_list_users` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-list-users.md
- `abs_zalo_readiness` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-readiness.md
- `abs_zalo_recent_messages` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-recent-messages.md
- `abs_zalo_refresh_discovery` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-refresh-discovery.md
- `abs_zalo_review_pending_member` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-review-pending-member.md
- `abs_zalo_search_stickers` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-search-stickers.md
- `abs_zalo_unblock_group_member` — Read — https://policylayer.com/tools/abs-zalo-bot/abs-zalo-unblock-group-member.md
- `zalo_list_groups` — Read — https://policylayer.com/tools/abs-zalo-bot/zalo-list-groups.md
- …and 12 more: https://policylayer.com/tools/abs-zalo-bot.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=abs-zalo-bot · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/abs-zalo-bot