This record as markdown: /tools/ra1nyxin-allcanuse-mcp/list-cameras.md
What list_cameras does on Allcanuse
AI agents call list_cameras to retrieve information from Allcanuse without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_cameras is rated Low
List operations are read-only with no side effects—they retrieve information about system resources (cameras) without altering state. The low severity reflects that camera enumeration poses minimal risk unless an adversary uses it to discover hardware for subsequent capture attacks, but listing alone causes no harm. Confidence is reduced due to the missing description, though the name is sufficiently clear.
From the tool's definition Tool name 'list_cameras' indicates a query/enumeration action. The description is empty, but the name strongly suggests retrieving or listing available camera devices without modifying them.
Attacks that exploit this kind of access
The rule that runs list_cameras safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Allcanuse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_cameras, this is the rule to start with:
list_cameras is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Allcanuse, apply this rule, and every list_cameras call is checked against it from then on.
Questions about list_cameras
list_cameras is a read tool on the Allcanuse MCP server. It is categorised as a Read tool in the Allcanuse MCP Server, which means it retrieves data without modifying state.
Register the Allcanuse MCP server in PolicyLayer and add a rule for list_cameras: 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 Allcanuse. Nothing to install.
list_cameras 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 list_cameras 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 list_cameras. 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.
list_cameras is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Allcanuse, and thousands of servers like it.
This server
Across the catalogue