New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

list_cameras

A read tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about list_cameras

What does the list_cameras tool do? +

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.

How do I enforce a policy on list_cameras? +

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.

What risk level is list_cameras? +

list_cameras is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_cameras? +

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.

How do I block list_cameras completely? +

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.

What MCP server provides list_cameras? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Allcanuse's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.