# get_status

Get site config + brand for an org.

Agent View of the PolicyLayer registry record for `get_status`. HTML page: https://policylayer.com/tools/9d9dev-mcp/get-status

## Facts

- Tool: `get_status`
- Server: 9d9dev (`@9d9dev/mcp`) — https://policylayer.com/tools/9d9dev-mcp.md
- Install: `npx -y @9d9dev/mcp`
- Homepage: https://www.npmjs.com/package/@9d9dev/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `org_id` | string | no | Optional. Defaults to the org_id in this project's .9d9.json — only pass to override. |

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

## Why get_status is rated Low

Even though get_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 get_status to retrieve information from 9d9dev 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 9d9dev:

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

## Other tools on 9d9dev (6)

- `get_config` — Read — https://policylayer.com/tools/9d9dev-mcp/get-config.md
- `list_deploys` — Read — https://policylayer.com/tools/9d9dev-mcp/list-deploys.md
- `activate_deploy` — Write — https://policylayer.com/tools/9d9dev-mcp/activate-deploy.md
- `attach_domain` — Write — https://policylayer.com/tools/9d9dev-mcp/attach-domain.md
- `save_api_key` — Write — https://policylayer.com/tools/9d9dev-mcp/save-api-key.md
- `update_brand` — Write — https://policylayer.com/tools/9d9dev-mcp/update-brand.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=9d9dev-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/9d9dev-mcp
