Check Node.js version compatibility and validate against package.json engines field
AI agents call nodejs_compatibility to retrieve information from MCP DevTools Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs validation and compatibility checking—typical Read operations that retrieve and analyze information. It does not create, modify, delete, or execute code/commands. The operations are informational with no side effects, placing it firmly in the Read category with low severity and high confidence.
From the tool's definition Tool description explicitly states it 'check[s]' and 'validate[s]' against package.json, indicating read-only operations that query/inspect Node.js version compatibility without modifying any data or triggering external operations.
Documented attack patterns abuse exactly the kind of access nodejs_compatibility gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP DevTools Server, and nothing reaches the server without passing your rules. This is the rule we recommend for nodejs_compatibility:
{
"version": "1",
"default": "deny",
"tools": {
"nodejs_compatibility": {}
}
}nodejs_compatibility 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.
Check Node.js version compatibility and validate against package.json engines field. It is categorised as a Read tool in the MCP DevTools Server MCP Server, which means it retrieves data without modifying state.
Register the MCP DevTools Server MCP server in PolicyLayer and add a rule for nodejs_compatibility: 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 MCP DevTools Server. Nothing to install.
nodejs_compatibility 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 nodejs_compatibility 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 nodejs_compatibility. 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.
nodejs_compatibility is provided by the MCP DevTools Server MCP server (rshade/mcp-devtools-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP DevTools Server, 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.
79 MCP DevTools Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.