设置 Apex 设备触觉反馈
AI agents use vicon_set_apex_feedback to create or update resources in Vicon DataStream MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vicon DataStream MCP Server environment.
This tool configures/sets haptic feedback parameters on an Apex device, which is a write/configuration operation. It modifies device state (haptic feedback settings) but is reversible as settings can be changed again. The blast radius is medium since misconfiguration could affect physical device behavior or ongoing motion capture sessions, but it does not destroy data or trigger irreversible actions.
From the tool's definition 设置 Apex 设备触觉反馈 (Set Apex device haptic feedback)
Attacks that exploit this kind of access
设置 Apex 设备触觉反馈. It is categorised as a Write tool in the Vicon DataStream MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vicon DataStream MCP Server MCP server in PolicyLayer and add a rule for vicon_set_apex_feedback: 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_set_apex_feedback is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vicon_set_apex_feedback 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_set_apex_feedback. 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_set_apex_feedback 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 →