camera_connect · Ascom MCP: Risk & Policy

WHAT IT DOES

What camera_connect does on Ascom

AI agents use camera_connect to create or update resources in Ascom — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ascom environment.

WHY IT NEEDS A POLICY

Why camera_connect needs a policy

Connecting to a camera establishes a connection/session state, which is a reversible write-like operation (it can be disconnected). It does not read data, execute commands, destroy data, or involve finances. The blast radius is low since it only initiates a device connection.

From the tool's definition Connect to an ASCOM camera

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

camera_connect Rate-limited

camera_connect stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "camera_connect": {
      "limits": [
        {
          "counter": "camera_connect_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ascom, so you can run agents against it safely.

FAQ

Questions about camera_connect

What does the camera_connect tool do? +

Connect to an ASCOM camera. It is categorised as a Write tool in the Ascom MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on camera_connect? +

Register the Ascom MCP server in PolicyLayer and add a rule for camera_connect: 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 Ascom. Nothing to install.

What risk level is camera_connect? +

camera_connect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit camera_connect? +

Yes. Add a rate_limit block to the camera_connect 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 camera_connect completely? +

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

camera_connect is provided by the Ascom MCP server (stellarpunk/mcp-server-ascom). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.