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).
This record as markdown: /tools/ai-clarx-mcp/analyze-clarx-manifest.md
What analyze_clarx_manifest does on Mcp
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
content | string | — | Raw JSON content. Pass this or file_path, not both. |
file_path | string | — | Path to clarx-manifest.json (resolved against the server working directory). |
Parameters from the server's own tool schema.
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 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 signalsAccepts file system path (file_path) · Accepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs analyze_clarx_manifest safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For analyze_clarx_manifest, this is the rule to start with:
analyze_clarx_manifest is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every analyze_clarx_manifest call is checked against it from then on.
Questions about 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). It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
analyze_clarx_manifest accepts 2 parameters: content, file_path. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for analyze_clarx_manifest: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp. Nothing to install.
analyze_clarx_manifest is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the analyze_clarx_manifest rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for analyze_clarx_manifest. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
analyze_clarx_manifest is provided by the MCP server (@clarxai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue