AT Protocol MCP Server

analyze_moderation_status

Read-only

Evaluate moderation status of a user or post to determine safety before rendering content. Returns content labels, moderation decisions, and personal blocks or mutes.

Instructions

Analyze moderation status of a post or user. Returns content labels, moderation decisions, and personal moderation state (blocks, mutes). Subject can be a DID (for users) or AT-URI (for posts). Works without authentication; richer with auth. Use this tool to evaluate safety before rendering content; use block_user or mute_user to act on the results. Subject to per-tool rate limiting.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`subject`	Yes	DID of a user account (e.g. did:plc:abc123) or AT-URI of a post (at://did/app.bsky.feed.post/rkey) to analyze.
`includeLabels`	No	Whether to fetch and include content labels in the response (default true). Set to false to skip label fetching for a faster call.

Output Schema

TableJSON Schema

Name	Required	Description
`success`	Yes	Whether the analysis completed successfully.
`subject`	Yes	The DID or AT-URI that was analyzed.
`subjectType`	Yes	"user" when subject is a DID; "post" when subject is an AT-URI.
`moderation`	Yes	Raw moderation state for the subject.
`analysis`	Yes	Derived safety analysis based on labels and moderation state.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.6.2Jun 23, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed3 schema fields changedv0.6.0Jun 11, 2026

addedInput schema / properties / includeLabels / description

Added value: +"Whether to fetch and include content labels in the response (default true). Set to false to skip label fetching for a faster call."

addedInput schema / properties / subject / description

Added value: +"DID of a user account (e.g. did:plc:abc123) or AT-URI of a post (at://did/app.bsky.feed.post/rkey) to analyze."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "analysis": {
+      "description": "Derived safety analysis based on labels and moderation state.",
+      "properties": {
+        "hasContentWarnings": {
+          "description": "True if any content warnings were detected.",
+          "type": "boolean"
+        },
+        "isNSFW": {
+          "description": "True if NSFW-related labels were found.",
+          "type": "boolean"
+        },
+        "isSpam": {
+          "description": "True if spam labels were found.",
+          "type": "boolean"
+        },
+        "requiresWarning": {
+          "description": "True if a warning should be shown before displaying content.",
+          "type": "boolean"
+        },
+        "safetyLevel": {
+          "description": "\"safe\" = no issues; \"warning\" = minor labels or muted; \"restricted\" = spam/hate; \"blocked\" = mutual or list block.",
+          "enum": [
+            "safe",
+            "warning",
+            "restricted",
+            "blocked"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "hasContentWarnings",
+        "isNSFW",
+        "isSpam",
+        "requiresWarning",
+        "safetyLevel"
+      ],
+      "type": "object"
+    },
+    "moderation": {
+      "description": "Raw moderation state for the subject.",
+      "properties": {
+        "blocked": {
+          "description": "True if you are blocking this account (user subjects only).",
+          "type": "boolean"
+        },
+        "blockedBy": {
+          "description": "True if this account is blocking you (user subjects only).",
+          "type": "boolean"
+        },
+        "blocking": {
+          "description": "AT-URI of your block record for this account, if any.",
+          "type": "string"
+        },
+        "blockingByList": {
+          "description": "Moderation list that caused the block, if applicable.",
+          "properties": {
+            "name": {
+              "description": "Display name of the list.",
+              "type": "string"
+            },
+            "uri": {
+              "description": "AT-URI of the list.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "uri"
+          ],
+          "type": "object"
+        },
+        "labels": {
+          "description": "Content labels attached to the subject (present when includeLabels=true and labels exist).",
+          "items": {
+            "properties": {
+              "cts": {
+                "description": "ISO-8601 timestamp when the label was created.",
+                "type": "string"
+              },
+              "src": {
+                "description": "DID of the labeler that issued this label.",
+                "type": "string"
+              },
+              "uri": {
+                "description": "AT-URI of the labeled record.",
+                "type": "string"
+              },
+              "val": {
+                "description": "Label value (e.g. \"nsfw\", \"spam\").",
+                "type": "string"
+              }
+            },
+            "required": [
+              "src",
+              "uri",
+              "val",
+              "cts"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "muted": {
+          "description": "True if you have muted this account (user subjects only).",
+          "type": "boolean"
+        },
+        "mutedByList": {
+          "description": "Moderation list that caused the mute, if applicable.",
+          "properties": {
+            "name": {
+              "description": "Display name of the list.",
+              "type": "string"
+            },
+            "uri": {
+              "description": "AT-URI of the list.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "uri"
+          ],
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "subject": {
+      "description": "The DID or AT-URI that was analyzed.",
+      "type": "string"
+    },
+    "subjectType": {
+      "description": "\"user\" when subject is a DID; \"post\" when subject is an AT-URI.",
+      "enum": [
+        "user",
+        "post"
+      ],
+      "type": "string"
+    },
+    "success": {
+      "description": "Whether the analysis completed successfully.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "subject",
+    "subjectType",
+    "moderation",
+    "analysis"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.3.0Jun 9, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedv0.2.1Jun 2, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true and openWorldHint=true; description adds that it works without auth but richer with auth, and mentions rate limiting. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, each adding value: purpose, returns, subject types, auth, rate limiting, usage guidance. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With output schema, return values are covered. Description covers subject types, auth dependency, rate limiting, and relationship to sibling tools. Complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds meaning: explains subject format (DID or AT-URI) and includeLabels effect (faster if false). Above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Analyze moderation status of a post or user' and lists return types. It distinguishes from sibling tools like block_user and mute_user.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this tool to evaluate safety before rendering content; use block_user or mute_user to act on the results.' Provides clear usage context and alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.