# check_status

Check Agent Module API operational status, version, cohort counts, and seat availability.

Agent View of the PolicyLayer registry record for `check_status`. HTML page: https://policylayer.com/tools/dev-agent-module-mcp/check-status

## Facts

- Tool: `check_status`
- Server: Agent Module (`https://api.agent-module.dev/mcp`) — https://policylayer.com/tools/dev-agent-module-mcp.md
- Homepage: https://github.com/AgentModule/mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server CORS policy: *
- 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": "check_status",
    "arguments": {}
  }
}
```

## Why check_status is rated Low

This tool retrieves system and service information without creating, modifying, deleting, or executing any operations. It is a pure information-gathering function with minimal risk; misuse would only expose non-sensitive status data.

From the tool's own definition: "Tool name 'check_status' and description stating it checks 'operational status, version, cohort counts, and seat availability' — all read-only queries with no modification or side effects."

## Use case

AI agents call check_status to retrieve information from Agent Module 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 Agent Module:

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

## Other tools on Agent Module (6)

- `join_waitlist` — Financial — https://policylayer.com/tools/dev-agent-module-mcp/join-waitlist.md
- `submit_referral` — Financial — https://policylayer.com/tools/dev-agent-module-mcp/submit-referral.md
- `query_knowledge` — Read — https://policylayer.com/tools/dev-agent-module-mcp/query-knowledge.md
- `get_trial_key` — Write — https://policylayer.com/tools/dev-agent-module-mcp/get-trial-key.md
- `register_interest` — Write — https://policylayer.com/tools/dev-agent-module-mcp/register-interest.md
- `submit_pov` — Write — https://policylayer.com/tools/dev-agent-module-mcp/submit-pov.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-agent-module-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-agent-module-mcp