Check whether node, genlayer, python, and genvm-lint are available to this MCP server.
AI agents call check_tools to retrieve information from Genlayer Cli without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a diagnostic/query tool that checks the presence and status of system tools and dependencies. It retrieves information about the execution environment's state but performs no side effects, modifications, or operations. It falls squarely into the Read category as it queries system state without altering it.
From the tool's definition Tool name 'check_tools' and description 'Check whether node, genlayer, python, and genvm-lint are available' indicates a passive query operation that verifies availability of executables/dependencies without modifying, executing, or deleting any resources.
Attacks that exploit this kind of access
Check whether node, genlayer, python, and genvm-lint are available to this MCP server. It is categorised as a Read tool in the Genlayer Cli MCP Server, which means it retrieves data without modifying state.
Register the Genlayer Cli MCP server in PolicyLayer and add a rule for check_tools: 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 Genlayer Cli. Nothing to install.
check_tools 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_tools 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_tools. 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_tools is provided by the Genlayer Cli MCP server (ngh1105/genlayer-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →