doc_drift_check

Compare canonical homelab docs with live Docker/systemd/Apache/monitoring inventory.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-control-plane/doc-drift-check.md

WHAT IT DOES

What doc_drift_check does on Mcp Control Plane

AI agents call doc_drift_check to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why doc_drift_check is rated Low

This tool performs a state verification/audit operation by reading and comparing documentation against current system state. No data is created, modified, deleted, or executed. The blast radius if misused is minimal—it can only reveal discrepancies in documentation or system state, not alter infrastructure or trigger operations.

From the tool's definition Tool compares canonical homelab docs with live inventory (Docker, systemd, Apache, monitoring). The verb 'Compare' and the read-only nature of inventory checks indicate data retrieval with no modifications, deletions, or command execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs doc_drift_check safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For doc_drift_check, this is the rule to start with:

doc_drift_check Allowed

doc_drift_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "doc_drift_check": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every doc_drift_check call is checked against it from then on.

FAQ

Questions about doc_drift_check

What does the doc_drift_check tool do? +

Compare canonical homelab docs with live Docker/systemd/Apache/monitoring inventory. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on doc_drift_check? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for doc_drift_check: 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 Control Plane. Nothing to install.

What risk level is doc_drift_check? +

doc_drift_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit doc_drift_check? +

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

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

doc_drift_check is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →