AI agents call get_ptz_preset to retrieve information from MCP Server - VMS Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves PTZ (pan-tilt-zoom) preset configurations from a CCTV system. Retrieval of preset metadata has no side effects and poses minimal risk—it only queries existing camera positioning data. The severity is low because misuse would allow querying preset locations but not executing uncontrolled camera movements or accessing unauthorized video streams.
From the tool's definition Tool name 'get_ptz_preset' and server description indicating PTZ preset management; sibling tool 'move_ptz_to_preset' suggests this retrieves preset configurations rather than modifying them. Description is empty, which reduces confidence slightly.
Documented attack patterns abuse exactly the kind of access get_ptz_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 get_ptz_preset:
{
"version": "1",
"default": "deny",
"tools": {
"get_ptz_preset": {}
}
}get_ptz_preset is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_ptz_preset. It is categorised as a Read tool in the MCP Server - VMS Integration MCP Server, which means it retrieves data without modifying state.
Register the MCP Server - VMS Integration MCP server in PolicyLayer and add a rule for get_ptz_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.
get_ptz_preset 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 get_ptz_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 get_ptz_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.
get_ptz_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.