Validates project documentation against standards. Checks for required files, valid frontmatter, broken dependencies, missing fields, and formatting issues. Can auto-fix common problems. Run this before commits to ensure documentation quality.
AI agents invoke lint_project_docs to trigger actions in Project MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool does more than passively read — it actively validates and can auto-fix documentation issues, meaning it may modify files in place. The 'auto-fix' capability constitutes a write/execute action beyond pure reading. The most severe applicable category is Execute since it triggers automated fixes and checks that can alter project state depending on arguments/options passed.
From the tool's definition 'Validates project documentation', 'Can auto-fix common problems', 'Run this before commits'
Documented attack patterns abuse exactly the kind of access lint_project_docs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Project MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for lint_project_docs:
{
"version": "1",
"default": "deny",
"tools": {
"lint_project_docs": {
"limits": [
{
"counter": "lint_project_docs_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}lint_project_docs stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Validates project documentation against standards. Checks for required files, valid frontmatter, broken dependencies, missing fields, and formatting issues. Can auto-fix common problems. Run this before commits to ensure documentation quality. It is categorised as a Execute tool in the Project MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Project MCP server in PolicyLayer and add a rule for lint_project_docs: 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 Project MCP. Nothing to install.
lint_project_docs 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 lint_project_docs 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 lint_project_docs. 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.
lint_project_docs is provided by the Project MCP server (pouyanafisi/project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Project MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
42 Project MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.