check_llm_status

Check whether the local llama.cpp server is running and reachable.

Server Excalidraw MCP Server jeel00dev/exclalidraw_mcp
Category Read
Risk class Low
Parameters 00 required

What check_llm_status does on Excalidraw MCP Server

AI agents call check_llm_status to retrieve information from Excalidraw MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_llm_status needs a policy

This tool queries the state of a local LLM server without modifying, executing, deleting, or affecting any external systems or data. It is purely informational, making it a Read category tool with low severity. The blast radius is minimal: at worst, an agent receives accurate or stale status information and may decide not to call generate_diagram if the server is unavailable.

From the tool's definition Tool name and description indicate it performs a status check operation: 'Check whether the local llama.cpp server is running and reachable.' This is a diagnostic query with no side effects—it only retrieves the operational status of a local service.

Questions about check_llm_status

What does the check_llm_status tool do? +

Check whether the local llama.cpp server is running and reachable. It is categorised as a Read tool in the Excalidraw MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_llm_status? +

Register the Excalidraw MCP Server MCP server in PolicyLayer and add a rule for check_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 Excalidraw MCP Server. Nothing to install.

What risk level is check_llm_status? +

check_llm_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_llm_status? +

Yes. Add a rate_limit block to the check_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.

How do I block check_llm_status completely? +

Set action: deny in the PolicyLayer policy for check_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.

What MCP server provides check_llm_status? +

check_llm_status is provided by the Excalidraw MCP Server MCP server (jeel00dev/exclalidraw_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.