Check camera system health and LM Studio availability
AI agents call check_system_status to retrieve information from OBSBOT Camera MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries system health metrics and service availability. It performs no side effects, makes no state changes, executes no external operations, and poses minimal risk. It is purely informational, fitting the Read category. Severity is low because even if an AI agent misuses this tool, it can only retrieve status data with no impact on camera control, data integrity, or other systems.
From the tool's definition Tool name 'check_system_status' and description 'Check camera system health and LM Studio availability' indicate a diagnostic query operation that retrieves status information without modifying, executing, or controlling physical devices.
Attacks that exploit this kind of access
Check camera system health and LM Studio availability. It is categorised as a Read tool in the OBSBOT Camera MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OBSBOT Camera MCP Server MCP server in PolicyLayer and add a rule for check_system_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 OBSBOT Camera MCP Server. Nothing to install.
check_system_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_system_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_system_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_system_status is provided by the OBSBOT Camera MCP Server MCP server (radar105/obsbot-camera-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 →