knowledge_check_resolve · DevFlow MCP Server MCP

WHAT IT DOES

What knowledge_check_resolve does on DevFlow MCP Server

AI agents use knowledge_check_resolve 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_check_resolve needs a policy

This tool resolves/modifies the state of knowledge-check warnings, which is a reversible write operation (changing resolution status). It does not delete data irreversibly, execute code, or move money. The Iron Law enforcement and backend POST call indicate a state update.

From the tool's definition Resolve a single knowledge-check warning manually... calling resolutionType= [implies setting a resolution state]; 'surgical overrides' of knowledge-check warnings

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

knowledge_check_resolve Rate-limited

knowledge_check_resolve 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_check_resolve": {
      "limits": [
        {
          "counter": "knowledge_check_resolve_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_check_resolve

What does the knowledge_check_resolve tool do? +

Resolve a single knowledge-check warning manually. In most cases you do NOT need this tool anymore — the pre-tool-use hook on flow_update auto-calls POST /api/projects/:id/knowledge/auto-resolve which applies the Iron Law in bulk (extend > create > intent_defer; never dismiss). Use this manual tool only for surgical overrides. Iron Law of the LLM-Wiki: extend > create > intent_defer > NEVER dismiss. The backend now ENFORCES this — calling resolutionType=. 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_check_resolve? +

Register the DevFlow MCP Server MCP server in PolicyLayer and add a rule for knowledge_check_resolve: 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_check_resolve? +

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

Can I rate-limit knowledge_check_resolve? +

Yes. Add a rate_limit block to the knowledge_check_resolve 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_check_resolve completely? +

Set action: deny in the PolicyLayer policy for knowledge_check_resolve. 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_check_resolve? +

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