AI agents invoke jitsi_start_recording to trigger actions in Jitsi. 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.
jitsi_start_recording triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
Start recording the meeting (screen capture). Returns the path where the recording will be saved. It is categorised as a Execute tool in the Jitsi MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jitsi MCP server in PolicyLayer and add a rule for jitsi_start_recording: 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 Jitsi. Nothing to install.
jitsi_start_recording 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 jitsi_start_recording 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 jitsi_start_recording. 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.
jitsi_start_recording is provided by the Jitsi MCP server (tntclaus/jitsi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.