stylelint
Runs Stylelint and returns structured diagnostics (file, line, column, rule, severity, message).
This record as markdown: /tools/io-github-dave-london-github/stylelint.md
What stylelint does on Github
AI agents invoke stylelint to trigger actions in Github. 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.
Why stylelint is rated High
The tool actively runs Stylelint, an external tool/process, against code. This constitutes execution of an external operation. While it is read-only in terms of data modification (it only lints and reports), it executes a process whose effects depend on arguments (which files/configs are targeted).
From the tool's definition 'Runs Stylelint' — the tool executes an external linting process and returns its output
Attacks that exploit this kind of access
The rule that runs stylelint safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Github, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stylelint, this is the rule to start with:
stylelint 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Github, apply this rule, and every stylelint call is checked against it from then on.
Questions about stylelint
Runs Stylelint and returns structured diagnostics (file, line, column, rule, severity, message). It is categorised as a Execute tool in the Github MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Github MCP server in PolicyLayer and add a rule for stylelint: 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 Github. Nothing to install.
stylelint 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 stylelint 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 stylelint. 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.
stylelint is provided by the Github MCP server (@paretools/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Github, and thousands of servers like it.
Across the catalogue