Report gateway process health: async-job manager state plus the resolved persistence configuration and paths.
AI agents call llm_process_health 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 is a diagnostic/monitoring tool that reads internal state and configuration. It has no side effects on data or operations. The blast radius of misuse is low — an attacker could gain awareness of system topology and job queue status, but cannot modify jobs, execute code, or destroy data. Categorized as Read because it retrieves and reports information only.
From the tool's definition The tool 'Report gateway process health: async-job manager state plus the resolved persistence configuration and paths' retrieves and reports current system state without modifying, executing external operations, or deleting data.
Documented attack patterns abuse exactly the kind of access llm_process_health 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 llm_process_health:
{
"version": "1",
"default": "deny",
"tools": {
"llm_process_health": {}
}
}llm_process_health 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 gateway process health: async-job manager state plus the resolved persistence configuration and paths. 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 llm_process_health: 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.
llm_process_health 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 llm_process_health 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 llm_process_health. 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.
llm_process_health 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.