Start new meeting session. Returns meeting ID.
AI agents invoke start_meeting to trigger actions in N2n Nexus. 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 an operation that creates and initiates a meeting session in the system. While not destructive or directly modifying persistent data, it represents an Execute action because it triggers external effects (meeting room instantiation, resource allocation, participant notification) that persist and depend on how the operation is invoked.
From the tool's definition "Start new meeting session" triggers an external operation (meeting creation) whose effects depend on arguments (meeting parameters). The tool initiates a real-time collaborative session within the n2n-nexus hub.
Documented attack patterns abuse exactly the kind of access start_meeting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and N2n Nexus, and nothing reaches the server without passing your rules. This is the rule we recommend for start_meeting:
{
"version": "1",
"default": "deny",
"tools": {
"start_meeting": {
"limits": [
{
"counter": "start_meeting_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start_meeting 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.
Start new meeting session. Returns meeting ID. It is categorised as a Execute tool in the N2n Nexus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the N2n Nexus MCP server in PolicyLayer and add a rule for start_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 N2n Nexus. Nothing to install.
start_meeting 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 start_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 start_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.
start_meeting is provided by the N2n Nexus MCP server (n2ns/n2n-nexus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from N2n Nexus, 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.
22 N2n Nexus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.