List all custom (user-defined) patterns loaded from your config file.
AI agents call list_custom_patterns to retrieve information from Classmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and returns configuration data about custom CSS patterns. It performs a simple lookup or enumeration of existing patterns without creating, modifying, deleting, or executing any operations. The verb 'list' is characteristic of Read category tools. The blast radius is minimal—the worst case is information disclosure about the user's CSS configuration, which is low-severity data exposure.
From the tool's definition Tool name 'list_custom_patterns' and description 'List all custom (user-defined) patterns loaded from your config file' indicate a retrieval/query operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_custom_patterns gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Classmcp, and nothing reaches the server without passing your rules. This is the rule we recommend for list_custom_patterns:
{
"version": "1",
"default": "deny",
"tools": {
"list_custom_patterns": {}
}
} list_custom_patterns 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.
List all custom (user-defined) patterns loaded from your config file. It is categorised as a Read tool in the Classmcp MCP Server, which means it retrieves data without modifying state.
Register the Class MCP server in PolicyLayer and add a rule for list_custom_patterns: 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 Classmcp. Nothing to install.
list_custom_patterns 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 list_custom_patterns 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 list_custom_patterns. 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.
list_custom_patterns is provided by the Class MCP server (thedecipherist/classmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Classmcp, 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.
10 Classmcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.