knowledge_draft_accept · DevFlow MCP Server MCP

WHAT IT DOES

What knowledge_draft_accept does on DevFlow MCP Server

AI agents use knowledge_draft_accept to create or update resources in DevFlow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DevFlow MCP Server environment.

WHY IT NEEDS A POLICY

Why knowledge_draft_accept needs a policy

This tool irreversibly commits a draft by creating a new ADR or documentation page and marking the draft as accepted. While it creates new artifacts (a Write operation), the description emphasizes it is a 'commit step' that should only be used when certain, indicating significant consequence.

From the tool's definition 'Creates the corresponding ADR or doc_page and marks the draft accepted. This is the commit step — use only when you are certain the draft is good to merge.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

knowledge_draft_accept Rate-limited

knowledge_draft_accept 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "knowledge_draft_accept": {
      "limits": [
        {
          "counter": "knowledge_draft_accept_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DevFlow MCP Server, so you can run agents against it safely.

FAQ

Questions about knowledge_draft_accept

What does the knowledge_draft_accept tool do? +

Accept a draft. Creates the corresponding ADR or doc_page and marks the draft accepted. This is the commit step — use only when you are certain the draft is good to merge. Normally users accept via the UI; this tool exists for autonomous workflows. It is categorised as a Write tool in the DevFlow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on knowledge_draft_accept? +

Register the DevFlow MCP Server MCP server in PolicyLayer and add a rule for knowledge_draft_accept: 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 DevFlow MCP Server. Nothing to install.

What risk level is knowledge_draft_accept? +

knowledge_draft_accept is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit knowledge_draft_accept? +

Yes. Add a rate_limit block to the knowledge_draft_accept 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.

How do I block knowledge_draft_accept completely? +

Set action: deny in the PolicyLayer policy for knowledge_draft_accept. 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.

What MCP server provides knowledge_draft_accept? +

knowledge_draft_accept is provided by the DevFlow MCP Server MCP server (klausfreiberufler/devflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.