LM Studioの接続状態を確認
AI agents call check_lm_studio_status to retrieve information from Translate SRT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only diagnostic check of the LM Studio connection state. It retrieves status information with no side effects, no code execution, no data modification, and no destructive operations. This is a classic Read category tool with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'check_lm_studio_status' and description 'LM Studioの接続状態を確認' (Check LM Studio connection status) indicate a status check operation that queries the state of an external service without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
LM Studioの接続状態を確認. It is categorised as a Read tool in the Translate SRT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Translate SRT MCP Server MCP server in PolicyLayer and add a rule for check_lm_studio_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 Translate SRT MCP Server. Nothing to install.
check_lm_studio_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 check_lm_studio_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 check_lm_studio_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.
check_lm_studio_status is provided by the Translate SRT MCP Server MCP server (sumik5/translate-srt-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 →