Stop an active video recording and finalize the file.
AI agents invoke bazel_ios_video_record_stop to trigger actions in XcodeBazelMCP. 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.
This tool executes a command that stops an ongoing external process (video recording) and finalizes output. While not destructive in itself (the recording still exists), it is not merely reading or writing data passively—it actively triggers a state change in an external system.
From the tool's definition Tool description indicates 'Stop an active video recording and finalize the file' - this triggers an external operation (stopping a video recording process on iOS simulator/device) whose effects are immediate and depend on the state of an active recording.
Documented attack patterns abuse exactly the kind of access bazel_ios_video_record_stop gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and XcodeBazelMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for bazel_ios_video_record_stop:
{
"version": "1",
"default": "deny",
"tools": {
"bazel_ios_video_record_stop": {
"limits": [
{
"counter": "bazel_ios_video_record_stop_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} bazel_ios_video_record_stop 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.
Stop an active video recording and finalize the file. It is categorised as a Execute tool in the XcodeBazelMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_ios_video_record_stop: 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 XcodeBazelMCP. Nothing to install.
bazel_ios_video_record_stop 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 bazel_ios_video_record_stop 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 bazel_ios_video_record_stop. 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.
bazel_ios_video_record_stop is provided by the XcodeBazel MCP server (xcodebazelmcp/xcodebazelmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from XcodeBazelMCP, 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.
117 XcodeBazelMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.