# edm_wiki_lint

Health check and trajectory pattern detection for significance wiki. Reports arc distribution, emotional weight stats, recurring themes, and missing fields.

Agent View of the PolicyLayer registry record for `edm_wiki_lint`. HTML page: https://policylayer.com/tools/deepadata-edm/edm-wiki-lint

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `wiki_path` | string | yes | Path to wiki directory |

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

## Why edm_wiki_lint is rated Low

This tool analyzes existing wiki data to provide diagnostic information and statistics. It retrieves and reports on metadata patterns without modifying, creating, or deleting any data. The analysis of recurring themes, missing fields, and emotional weight statistics are all read-only query operations with no side effects.

From the tool's own definition: "Tool performs 'Health check and trajectory pattern detection' and 'Reports' on wiki data. The verbs indicate read-only analysis: checking health, detecting patterns, reporting statistics (arc distribution, emotional weight stats, recurring themes, missing…"

## Use case

AI agents call edm_wiki_lint to retrieve information from Deepadata Edm 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 Deepadata Edm:

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

## Other tools on Deepadata Edm (8)

- `deepadata_activate` — Read — https://policylayer.com/tools/deepadata-edm/deepadata-activate.md
- `deepadata_activate_reason` — Read — https://policylayer.com/tools/deepadata-edm/deepadata-activate-reason.md
- `edm_project` — Read — https://policylayer.com/tools/deepadata-edm/edm-project.md
- `edm_wiki_search` — Read — https://policylayer.com/tools/deepadata-edm/edm-wiki-search.md
- `extract_from_content` — Read — https://policylayer.com/tools/deepadata-edm/extract-from-content.md
- `validate_edm` — Read — https://policylayer.com/tools/deepadata-edm/validate-edm.md
- `edm_wiki_generate` — Write — https://policylayer.com/tools/deepadata-edm/edm-wiki-generate.md
- `seal_artifact` — Write — https://policylayer.com/tools/deepadata-edm/seal-artifact.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=deepadata-edm · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deepadata-edm