AI agents call get_litellm_status to retrieve information from Homelab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about a LiteLLM proxy service without creating, modifying, deleting, executing commands, or committing financial operations. It is a pure read operation with minimal security risk—knowing the status of a proxy does not enable malicious actions or data exfiltration. Low severity because an AI agent obtaining proxy status is unlikely to cause harm even if misused.
From the tool's definition Tool name 'get_litellm_status' and description 'Check LiteLLM proxy status' indicate a status query operation with no modification of state.
Attacks that exploit this kind of access
Check LiteLLM proxy status. It is categorised as a Read tool in the Homelab MCP Server, which means it retrieves data without modifying state.
Register the Homelab MCP server in PolicyLayer and add a rule for get_litellm_status: 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 Homelab. Nothing to install.
get_litellm_status 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 get_litellm_status 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 get_litellm_status. 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.
get_litellm_status is provided by the Homelab MCP server (myraffy/homelab-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 →