generate_manifest_draft
Generate a first-draft agent manifest (CLAUDE.md / AGENTS.md / GEMINI.md) grounded in the repository README and description. Uses your ANTHROPIC_API_KEY. Claims the model cannot ground are marked as TODO comments.
This record as markdown: /tools/ai-clarx-mcp/generate-manifest-draft.md
What generate_manifest_draft does on Mcp
AI agents use generate_manifest_draft to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
filename | string | Yes | Manifest filename to draft. |
repo_name | string | — | |
repo_readme | string | — | README content for grounding (max ~6000 chars used). Required unless repo_description is present. |
repo_description | string | null | — |
Parameters from the server's own tool schema.
Why generate_manifest_draft is rated Medium
The tool creates or generates new manifest files (CLAUDE.md, AGENTS.md, GEMINI.md) based on repository metadata. This is a reversible Write operation—generated drafts can be edited, deleted, or replaced. It does not execute code, delete data, move money, or trigger external operations with uncontrolled side effects.
From the tool's definition Tool 'generates' a 'first-draft' manifest file with 'TODO comments', explicitly creating new structured content in a repository without destructive overwrite semantics.
Risk signalsAccepts file system path (filename)
Attacks that exploit this kind of access
The rule that runs generate_manifest_draft 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 generate_manifest_draft, this is the rule to start with:
generate_manifest_draft stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 generate_manifest_draft call is checked against it from then on.
Questions about generate_manifest_draft
Generate a first-draft agent manifest (CLAUDE.md / AGENTS.md / GEMINI.md) grounded in the repository README and description. Uses your ANTHROPIC_API_KEY. Claims the model cannot ground are marked as TODO comments. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
generate_manifest_draft accepts 4 parameters: filename, repo_name, repo_readme, repo_description. Required: filename. 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 generate_manifest_draft: 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.
generate_manifest_draft is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_manifest_draft 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 generate_manifest_draft. 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.
generate_manifest_draft 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