Analyze all CSS files in a project directory. Finds all .css files recursively, combines them, and analyzes as a whole. Accepts: single file path, directory path, or glob pattern (e.g.,
AI agents call analyze_project_css to retrieve information from CSS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and inspects CSS files to provide analysis—a purely informational operation with no side effects. It accepts input paths but does not create, modify, delete, or execute arbitrary code. The blast radius of misuse is minimal; worst case, an agent could analyze unintended CSS files, but no data is at risk of loss or corruption.
From the tool's definition Tool description states it 'Analyze[s] all CSS files in a project directory' and 'Finds all .css files recursively, combines them, and analyzes as a whole.' The verb 'analyze' combined with 'finds' and 'combines' indicates data retrieval and inspection with…
Documented attack patterns abuse exactly the kind of access analyze_project_css gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CSS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_project_css:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_project_css": {}
}
}analyze_project_css is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyze all CSS files in a project directory. Finds all .css files recursively, combines them, and analyzes as a whole. Accepts: single file path, directory path, or glob pattern (e.g.,. It is categorised as a Read tool in the CSS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CSS MCP Server MCP server in PolicyLayer and add a rule for analyze_project_css: 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 CSS MCP Server. Nothing to install.
analyze_project_css 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 analyze_project_css 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 analyze_project_css. 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.
analyze_project_css is provided by the CSS MCP Server MCP server (stolinski/css-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 CSS MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 CSS MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.