Stop the bot from transcribing a live meeting. Replicates the exact same flow the Gantta web app uses when a user clicks the Stop button: (1) POST /api/bot/stop/<session_id> halts audio capture, (2) RPC meeting_ai.finalize_meeting transitions the meeting status from RECORDING to PENDING. No summa...
Part of the Gantta MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke bot_stop_meeting to trigger processes or run actions in Gantta. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
bot_stop_meeting can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
bot_stop_meeting:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Gantta policy for all 26 tools.
Agents calling execute-class tools like bot_stop_meeting have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
bot_stop_meeting is one of the high-risk operations in Gantta. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Stop the bot from transcribing a live meeting. Replicates the exact same flow the Gantta web app uses when a user clicks the Stop button: (1) POST /api/bot/stop/<session_id> halts audio capture, (2) RPC meeting_ai.finalize_meeting transitions the meeting status from RECORDING to PENDING. No summary is generated here — the AI client can separately call get_meeting to read the transcript and present it to the user in chat. Meeting stays at PENDING (ready to view, no summary run).. It is categorised as a Execute tool in the Gantta MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for bot_stop_meeting. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Gantta MCP server.
bot_stop_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 bot_stop_meeting rule in your Intercept 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 Intercept policy for bot_stop_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.
bot_stop_meeting is provided by the Gantta MCP server (gantta/gantta-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept