node_camera_snap

Take a photo using a mobile companion

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/node-camera-snap.md

WHAT IT DOES

What node_camera_snap does on CoWork OS

AI agents invoke node_camera_snap to trigger actions in CoWork OS. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why node_camera_snap is rated High

This tool executes an action on an external device (mobile companion), triggering the camera to capture a photo. It is not a simple read/query — it actively initiates a hardware operation. The blast radius is medium since it could capture images without explicit user awareness, raising privacy concerns, but it does not delete data or move money.

From the tool's definition 'Take a photo using a mobile companion' — triggers an external hardware operation (camera capture) on a mobile device

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs node_camera_snap safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For node_camera_snap, this is the rule to start with:

node_camera_snap Rate-limited

node_camera_snap stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "node_camera_snap": {
      "limits": [
        {
          "counter": "node_camera_snap_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every node_camera_snap call is checked against it from then on.

FAQ

Questions about node_camera_snap

What does the node_camera_snap tool do? +

Take a photo using a mobile companion. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on node_camera_snap? +

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

What risk level is node_camera_snap? +

node_camera_snap is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit node_camera_snap? +

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

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

node_camera_snap is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →