# validate_edm

Validate an EDM artifact against the v0.8.3 schema and governance rules. Returns validation errors and warnings.

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

## Facts

- Tool: `validate_edm`
- 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: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `strict` | boolean | no | Enable strict validation mode |
| `artifact` | object | yes | The EDM artifact to validate |

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

## Why validate_edm is rated Low

The tool performs schema validation and checks governance rules, returning diagnostic output (errors and warnings). This is a read-only inspection operation with no side effects on data or systems. No data is created, modified, deleted, executed, or financially affected. The lowest severity applies because misuse by an AI agent would only surface incorrect validation results, not cause damage.

From the tool's own definition: "Tool description states it 'Validate[s] an EDM artifact against the v0.8.3 schema and governance rules. Returns validation errors and warnings.' The verb is 'validate' which performs inspection and returns information without modifying, creating, deleting,…"

## Use case

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

## 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_lint` — Read — https://policylayer.com/tools/deepadata-edm/edm-wiki-lint.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
- `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