DF-312 — Health-report of the wiki: stale (release-stage entries older than N days that are still cited), orphan (entries with no in/out wiki-links), contradictions (deprecated/superseded ADRs that newer sources still cite). Use periodically (or before a major refactor) to keep the wiki clean. Re...
AI agents call wiki_get_lint to retrieve information from DevFlow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes wiki metadata to detect quality issues. It has no side effects—it does not create, modify, delete, or execute operations. The blast radius of misuse is minimal: an AI agent running this tool repeatedly would only generate diagnostic reports, not harm data or systems. This is a straightforward Read operation.
From the tool's definition Tool performs health-report analysis of wiki entries, identifying stale, orphan, and contradictory entries. Operations are purely diagnostic: queries and reports on wiki state without modifying, deleting, or executing external actions.
Attacks that exploit this kind of access
DF-312 — Health-report of the wiki: stale (release-stage entries older than N days that are still cited), orphan (entries with no in/out wiki-links), contradictions (deprecated/superseded ADRs that newer sources still cite). Use periodically (or before a major refactor) to keep the wiki clean. Resolve findings via the devflow-wiki-lint skill — never delete entries, always extend / cross-link / re-classify. It is categorised as a Read tool in the DevFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevFlow MCP Server MCP server in PolicyLayer and add a rule for wiki_get_lint: 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.
wiki_get_lint 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 wiki_get_lint 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 wiki_get_lint. 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.
wiki_get_lint 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →