Get SSR/hydration safety information for a class pattern. Use this when building SSR/Next.js/Nuxt/Remix applications to avoid hydration mismatches.
AI agents call get_ssr_info 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 queries existing metadata about CSS class patterns and their SSR compatibility. It has no side effects, does not execute code, does not modify data, and does not create financial obligations. It is a straightforward informational lookup, consistent with the 'Read' category for tools that retrieve or query data without side effects.
From the tool's definition Tool retrieves SSR/hydration safety information without modifying state or triggering side effects. The description explicitly states 'Get' information, and the use case is for checking safety during development, not for executing operations or modifying…
Documented attack patterns abuse exactly the kind of access get_ssr_info 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 get_ssr_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_ssr_info": {}
}
} get_ssr_info 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.
Get SSR/hydration safety information for a class pattern. Use this when building SSR/Next.js/Nuxt/Remix applications to avoid hydration mismatches. 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 get_ssr_info: 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.
get_ssr_info 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 get_ssr_info 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 get_ssr_info. 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.
get_ssr_info 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.