AI agents use jitsi_toggle_video to create or update resources in Jitsi — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jitsi environment.
An AI agent can call jitsi_toggle_video faster than any human can review — one bad instruction and it creates or modifies resources in Jitsi by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Toggle or set the camera on/off state. It is categorised as a Write tool in the Jitsi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jitsi MCP server in PolicyLayer and add a rule for jitsi_toggle_video: 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_toggle_video is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the jitsi_toggle_video 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_toggle_video. 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_toggle_video 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.