Check Deno installation and version info. Use for troubleshooting code execution issues or verifying runtime capabilities.
AI agents call check_deno_version to retrieve information from Code Mode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system metadata about the Deno runtime environment without side effects, code execution, or data modification. It is fundamentally a diagnostic query (similar to 'get' or 'fetch') used for troubleshooting.
From the tool's definition Tool performs 'Check Deno installation and version info' with no modification or execution capabilities—purely diagnostic/informational action that queries runtime state.
Documented attack patterns abuse exactly the kind of access check_deno_version gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Code Mode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_deno_version:
{
"version": "1",
"default": "deny",
"tools": {
"check_deno_version": {}
}
}check_deno_version 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 Deno installation and version info. Use for troubleshooting code execution issues or verifying runtime capabilities. It is categorised as a Read tool in the Code Mode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Code Mode MCP Server MCP server in PolicyLayer and add a rule for check_deno_version: 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 Code Mode MCP Server. Nothing to install.
check_deno_version 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 check_deno_version 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 check_deno_version. 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.
check_deno_version is provided by the Code Mode MCP Server MCP server (jx-codes/codemode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Code Mode MCP 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.
3 Code Mode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.