stopMeetingScribe
Stop a running meeting scribe: the bot leaves the meeting and the board is finalised (tidy pass plus a summary frame). Give it the sessionId returned by startMeetingScribe. Billing stops at the current block; the user can also stop the scribe simply by removing the bot from the meeting.
This record as markdown: /tools/io-stablebaseline-sb/stopmeetingscribe.md
What stopMeetingScribe does on Stable Baseline
AI agents invoke stopMeetingScribe to trigger actions in Stable Baseline. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
sessionId | string | Yes | The meeting scribe session to stop, as returned by startMeetingScribe. |
Parameters from the server's own tool schema.
Why stopMeetingScribe is rated High
This tool triggers an external operation — stopping a running bot process, finalizing a board, and halting billing. It causes side effects beyond simple data reads or writes: it terminates an active session, modifies billing state, and finalizes content. While it mentions billing stopping, it doesn't move money or commit new financial obligations; it ends an ongoing charge.
From the tool's definition Stop a running meeting scribe: the bot leaves the meeting and the board is finalised (tidy pass plus a summary frame). Billing stops at the current block.
Attacks that exploit this kind of access
The rule that runs stopMeetingScribe safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stopMeetingScribe, this is the rule to start with:
stopMeetingScribe 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every stopMeetingScribe call is checked against it from then on.
Questions about stopMeetingScribe
Stop a running meeting scribe: the bot leaves the meeting and the board is finalised (tidy pass plus a summary frame). Give it the sessionId returned by startMeetingScribe. Billing stops at the current block; the user can also stop the scribe simply by removing the bot from the meeting. It is categorised as a Execute tool in the Stable Baseline MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
stopMeetingScribe accepts 1 parameter: sessionId. Required: sessionId. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for stopMeetingScribe: 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 Stable Baseline. Nothing to install.
stopMeetingScribe 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 stopMeetingScribe 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 stopMeetingScribe. 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.
stopMeetingScribe is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
Across the catalogue