Run a lint check on the knowledge wiki to identify stale, low-coverage, or broken articles. Requires orchestrator role. Optionally scoped to a project. Each issue category is capped at max_per_category (default 50) with true totals exposed in summary.total_per_category and per-category truncated ...
Part of the Loopctl MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke knowledge_lint to trigger processes or run actions in Loopctl. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
knowledge_lint can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
knowledge_lint:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Loopctl policy for all 49 tools.
Agents calling execute-class tools like knowledge_lint have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
knowledge_lint is one of the high-risk operations in Loopctl. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Run a lint check on the knowledge wiki to identify stale, low-coverage, or broken articles. Requires orchestrator role. Optionally scoped to a project. Each issue category is capped at max_per_category (default 50) with true totals exposed in summary.total_per_category and per-category truncated flags.. It is categorised as a Execute tool in the Loopctl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for knowledge_lint. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Loopctl MCP server.
knowledge_lint is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the knowledge_lint rule in your Intercept 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 Intercept policy for knowledge_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.
knowledge_lint is provided by the Loopctl MCP server (loopctl-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept