AI agents call leave_meeting to permanently remove resources in Joinly — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Leaving a meeting is an irreversible action in context — once the AI agent leaves, the session participation ends and cannot be undone without rejoining (which may not always be possible, e.g., if the meeting has ended or re-entry is restricted). The blast radius is medium: it disrupts an ongoing meeting session but doesn't delete data. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'leave_meeting'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access leave_meeting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Joinly, and nothing reaches the server without passing your rules. This is the rule we recommend for leave_meeting:
{
"version": "1",
"default": "deny",
"hide": [
"leave_meeting"
]
}leave_meeting disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
leave_meeting. It is categorised as a Destructive tool in the Joinly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Joinly MCP server in PolicyLayer and add a rule for leave_meeting: 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 Joinly. Nothing to install.
leave_meeting 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 leave_meeting 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 leave_meeting. 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.
leave_meeting is provided by the Joinly MCP server (joinly-ai/joinly). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Joinly, 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.
12 Joinly tools catalogued and risk-classified — across an index of 43,000+ MCP servers.