# analyze_clarx_manifest

Validate a clarx-manifest.json machine manifest against the Clarx engine schema. Returns recognized keys, errors, and suggestions for keys worth declaring (generated dirs, hubs, verification commands).

Agent View of the PolicyLayer registry record for `analyze_clarx_manifest`. HTML page: https://policylayer.com/tools/ai-clarx-mcp/analyze-clarx-manifest

## Facts

- Tool: `analyze_clarx_manifest`
- Server: Mcp (`@clarxai/mcp`) — https://policylayer.com/tools/ai-clarx-mcp.md
- Install: `npx -y @clarxai/mcp`
- Homepage: https://github.com/Gernika-Labs/clarx-cloud
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 2
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `content` | string | no | Raw JSON content. Pass this or file_path, not both. |
| `file_path` | string | no | Path to clarx-manifest.json (resolved against the server working 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": "analyze_clarx_manifest",
    "arguments": {}
  }
}
```

## Why analyze_clarx_manifest is rated Low

This tool reads and analyzes a clarx-manifest.json file against a schema, returning diagnostic information. It performs no data modification, deletion, execution of commands, or financial operations. The action is purely analytical and informational, making it a Read category tool with low severity.

From the tool's own definition: "Tool performs validation and analysis of a manifest file, returning recognized keys, errors, and suggestions. Keywords: 'Validate', 'Returns recognized keys, errors, and suggestions' indicate data retrieval and analysis with no modifications or side effects."

Risk signals: Accepts file system path (file_path) · Accepts raw HTML/template content (content)

## Use case

AI agents call analyze_clarx_manifest to retrieve information from Mcp 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 Mcp:

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

## Other tools on Mcp (4)

- `analyze_manifest` — Read — https://policylayer.com/tools/ai-clarx-mcp/analyze-manifest.md
- `generate_manifest_draft` — Write — https://policylayer.com/tools/ai-clarx-mcp/generate-manifest-draft.md
- `get_ci_workflow` — Write — https://policylayer.com/tools/ai-clarx-mcp/get-ci-workflow.md
- `suggest_manifest_fix` — Write — https://policylayer.com/tools/ai-clarx-mcp/suggest-manifest-fix.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=ai-clarx-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ai-clarx-mcp