# list_numbers

List active sessions, optionally filtered by agent_id. Use this to check for leaked sessions or inspect what numbers are currently active in your account.

Agent View of the PolicyLayer registry record for `list_numbers`. HTML page: https://policylayer.com/tools/dev-agentsim-mcp/list-numbers

## Facts

- Tool: `list_numbers`
- Server: Mcp (`https://mcp.agentsim.dev/mcp`) — https://policylayer.com/tools/dev-agentsim-mcp.md
- Homepage: https://github.com/agentsimdev/agentsim-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `agent_id` | object | no |  |

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": "list_numbers",
    "arguments": {}
  }
}
```

## Why list_numbers is rated Low

This tool retrieves information about active mobile number sessions and agent associations without creating, modifying, deleting, or executing any operations. It has no side effects and is purely informational, making it a Read operation. Severity is low because exposure only reveals metadata about existing sessions rather than enabling unauthorized actions or data destruction.

From the tool's own definition: "Tool name is 'list_numbers' and description states 'List active sessions' with use case to 'check for leaked sessions or inspect what numbers are currently active'."

## Use case

AI agents call list_numbers 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": {
    "list_numbers": {}
  }
}
```

## Other tools on Mcp (4)

- `release_number` — Destructive — https://policylayer.com/tools/dev-agentsim-mcp/release-number.md
- `get_messages` — Read — https://policylayer.com/tools/dev-agentsim-mcp/get-messages.md
- `wait_for_otp` — Read — https://policylayer.com/tools/dev-agentsim-mcp/wait-for-otp.md
- `provision_number` — Write — https://policylayer.com/tools/dev-agentsim-mcp/provision-number.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=dev-agentsim-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-agentsim-mcp