Report installed provider CLI versions, availability, and login status for all five providers or one.
AI agents call cli_versions to retrieve information from LLM CLI Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports metadata about installed CLI tools, their versions, and availability status. It performs only read operations—no data is created, modified, deleted, or executed. The login status check is informational only. Blast radius is minimal since misuse would only expose version and status information already available to the system administrator.
From the tool's definition Tool name 'cli_versions' and description 'Report installed provider CLI versions, availability, and login status' indicate querying/retrieving status information with no side effects.
Documented attack patterns abuse exactly the kind of access cli_versions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LLM CLI Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for cli_versions:
{
"version": "1",
"default": "deny",
"tools": {
"cli_versions": {}
}
}cli_versions 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.
Report installed provider CLI versions, availability, and login status for all five providers or one. It is categorised as a Read tool in the LLM CLI Gateway MCP Server, which means it retrieves data without modifying state.
Register the LLM CLI Gateway MCP server in PolicyLayer and add a rule for cli_versions: 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 LLM CLI Gateway. Nothing to install.
cli_versions 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 cli_versions 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 cli_versions. 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.
cli_versions is provided by the LLM CLI Gateway MCP server (llm-cli-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LLM CLI Gateway, 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.
46 LLM CLI Gateway tools catalogued and risk-classified — across an index of 43,000+ MCP servers.