// SCAN REPORT

So Dsc

23 tools. 16 can modify or destroy data without limits.

16 write tools that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

16 can modify or destroy data

7 read-only

23 tools total

Community server · catalogue entry verified 30/06/2026

How to control So Dsc ↓

TOOL MAP

What So Dsc exposes to your agents

Read (7) Write / Execute (16) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous So Dsc tools

Execute · High start_bulb The tool executes a real-world physical action (opening the camera shutter) that affects the external environment. Execute · High start_burst This tool remotely executes a camera action that produces observable external effects (photos capture). Execute · High start_movie_rec This tool remotely triggers a camera to start recording video—an external operation with side effects that cannot be trivially reversed (requires stopping the recording separately). Execute · Medium stop_bulb This tool executes a command to a remote camera device that produces a physical side effect (shutter closure).

16 of So Dsc's 23 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control So Dsc

PolicyLayer is an MCP gateway — it sits between your AI agents and So Dsc, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "set_exposure_compensation": {
    "limits": [
      {
        "counter": "set_exposure_compensation_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "download_camera_picture": {
    "limits": [
      {
        "counter": "download_camera_picture_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register So Dsc — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SO DSC →

Instant setup, no code required.

FULL CATALOGUE

All 23 So Dsc tools

EXECUTE 10 tools

Execute half_press half_press Execute reconnect Force a full reconnect to the camera. Use after a power-cycle or Execute start_bulb Open the shutter for bulb exposure. Camera must be in Manual Execute start_burst Start continuous (burst) shooting. Camera must already be in still Execute start_movie_rec start_movie_rec Execute stop_bulb Close the bulb shutter. Execute stop_burst Stop a running burst. Returns the list of postview URLs (one per Execute stop_movie_rec Stop in-progress movie recording. Returns a postview URL (small Execute take_picture take_picture Execute zoom Zoom the lens.

WRITE 6 tools

Write set_exposure_compensation Exposure compensation in 1/3 EV steps (typical range: -9 to +9, = Write set_fnumber Set aperture (f-number) as a string like "5.6". Only honored in Write set_iso Set ISO. Pass a string the camera advertises — typically "AUTO", Write set_shutter Set shutter speed. Strings like "1/250", "1/4", "2", "BULB". Write set_white_balance_auto Switch white balance to Auto WB. Write set_white_balance_kelvin Lock white balance to a specific color temperature in kelvin

READ 7 tools

Read download_camera_picture Download a camera-side picture (full resolution from SD card) to Read get_liveview_frame Return the latest live preview JPEG (~640x424, ~35KB on RX100M5A). Read get_saved_picture Return a previously-saved picture (file under downloads/) as an Read get_status Report current camera state: liveview running, last frame age, mode, Read list_camera_pictures list_camera_pictures Read list_saved_pictures List pictures saved on the host (downloads/ directory). These are Read refresh_services refresh_services

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about So Dsc

How do I prevent bulk modifications through So Dsc? +

The So Dsc server has 6 write tools including set_exposure_compensation, set_fnumber, set_iso. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach So Dsc.

How many tools does the So Dsc MCP server expose? +

23 tools across 3 categories: Execute, Read, Write. 7 are read-only. 16 can modify, create, or delete data.

How do I enforce a policy on So Dsc? +

Register the So Dsc MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every So Dsc tool call.

Deterministic rules across all 23 So Dsc tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SO DSC →

Instant setup, no code required.

23 So Dsc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.