close_connection
Close a video connection and release resources.
This record as markdown: /tools/13rac1-videocapture-mcp/close-connection.md
What close_connection does on Video Still Capture MCP
AI agents call close_connection to permanently remove resources in Video Still Capture MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why close_connection is rated Critical
Closing a connection and releasing resources is an irreversible operation — once the camera connection is closed, any ongoing capture session is terminated and its state is lost. The word 'release' implies freeing hardware/software resources that cannot be undone without explicitly reopening the connection.
From the tool's definition Close a video connection and release resources
Attacks that exploit this kind of access
The rule that runs close_connection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Video Still Capture MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For close_connection, this is the rule to start with:
close_connection is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Video Still Capture MCP, apply this rule, and every close_connection call is checked against it from then on.
Questions about close_connection
Close a video connection and release resources. It is categorised as a Destructive tool in the Video Still Capture MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Video Still Capture MCP server in PolicyLayer and add a rule for close_connection: 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 Video Still Capture MCP. Nothing to install.
close_connection is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the close_connection 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 close_connection. 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.
close_connection is provided by the Video Still Capture MCP server (13rac1/videocapture-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Video Still Capture, and thousands of servers like it.
Across the catalogue