AI agents invoke move_ptz_to_preset to trigger actions in MCP Server - VMS Integration. 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.
Moving a PTZ camera to a preset is an external physical operation — it actuates real-world hardware (a camera's motorized pan/tilt/zoom mechanism). This is an Execute-category action as it triggers an external operation. Severity is high because misuse could redirect surveillance cameras away from monitored areas, potentially creating security blind spots.
From the tool's definition Tool name 'move_ptz_to_preset' on a server that controls PTZ (pan-tilt-zoom) camera presets, as described in the server description: 'control cameras with PTZ presets'
Documented attack patterns abuse exactly the kind of access move_ptz_to_preset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server - VMS Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for move_ptz_to_preset:
{
"version": "1",
"default": "deny",
"tools": {
"move_ptz_to_preset": {
"limits": [
{
"counter": "move_ptz_to_preset_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}move_ptz_to_preset 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.
Free to start. No card required.
move_ptz_to_preset. It is categorised as a Execute tool in the MCP Server - VMS Integration MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Server - VMS Integration MCP server in PolicyLayer and add a rule for move_ptz_to_preset: 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 MCP Server - VMS Integration. Nothing to install.
move_ptz_to_preset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the move_ptz_to_preset 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 move_ptz_to_preset. 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.
move_ptz_to_preset is provided by the MCP Server - VMS Integration MCP server (jyjune/mcp_vms). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server - VMS Integration, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 MCP Server - VMS Integration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.