获取相机列表
AI agents call vicon_get_cameras to retrieve information from Vicon DataStream MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about available cameras in the Vicon motion capture system. It performs a data query operation without modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could only discover what cameras are available, which is non-sensitive system metadata in a motion capture context.
From the tool's definition Tool name 'vicon_get_cameras' and description indicating it retrieves/gets a list of cameras. The description translates to 'get camera list' in English, which is a query operation with no side effects.
Attacks that exploit this kind of access
获取相机列表. It is categorised as a Read tool in the Vicon DataStream MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vicon DataStream MCP Server MCP server in PolicyLayer and add a rule for vicon_get_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 Vicon DataStream MCP Server. Nothing to install.
vicon_get_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 vicon_get_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 vicon_get_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.
vicon_get_cameras is provided by the Vicon DataStream MCP Server MCP server (ros-claw/vicon-datastream-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →