AI agents call get_status to retrieve information from So Dsc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports the current state of the camera (liveview status, frame age, mode) without any side effects, modifications, or control actions. It is purely informational—a status check operation. While it is part of a camera control system, this specific tool does not execute commands, modify settings, or perform destructive actions.
From the tool's definition Tool name 'get_status' and description 'Report current camera state' indicate a query operation that retrieves camera state information without modifying or executing operations on the device.
Attacks that exploit this kind of access
Report current camera state: liveview running, last frame age, mode,. It is categorised as a Read tool in the So Dsc MCP Server, which means it retrieves data without modifying state.
Register the So Dsc MCP server in PolicyLayer and add a rule for get_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 So Dsc. Nothing to install.
get_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_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_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_status is provided by the So Dsc MCP server (nananek/so-dsc). 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 →