Verifica el estado de conexión con el servidor LLM y lista los modelos disponibles
AI agents call llm_status to retrieve information from LLM MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs status checks and model enumeration—purely informational queries with no side effects, data modification, code execution, or destructive capability. It is a diagnostic/monitoring tool that returns current state and available resource information.
From the tool's definition Tool description indicates 'Verifica el estado de conexión' (verify connection status) and 'lista los modelos disponibles' (list available models). Both are read operations that retrieve information without modifying or executing anything.
Attacks that exploit this kind of access
Verifica el estado de conexión con el servidor LLM y lista los modelos disponibles. It is categorised as a Read tool in the LLM MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the LLM MCP Bridge MCP server in PolicyLayer and add a rule for llm_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 LLM MCP Bridge. Nothing to install.
llm_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 llm_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 llm_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.
llm_status is provided by the LLM MCP Bridge MCP server (ramgeart/llm-mcp-bridge). 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 →