create_meeting_bot

THE RISK

High Risk

Why create_meeting_bot needs a policy

This tool initiates an external agent action: deploying a bot into a live meeting, which has real-world side effects including joining a call uninvited, recording participants (potential privacy/legal implications), and transcribing conversations. The effects depend on arguments (meeting URL/credentials) and involve external operations beyond simple data writes.

From the tool's definition 'Create a bot to join a meeting and record/transcribe it' — triggers an external operation (bot joins a live video call and begins recording/transcribing participants)

Documented attack patterns abuse exactly the kind of access create_meeting_bot gives an agent:

POLICY

How to control create_meeting_bot

PolicyLayer is an MCP gateway — it sits between your AI agents and Attendee MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_meeting_bot:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_meeting_bot": {
      "limits": [
        {
          "counter": "create_meeting_bot_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

create_meeting_bot 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.

Create a free account and register Attendee MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Attendee MCP Server tools

Destructive delete_bot_data Delete all data associated with a bot (recordings, transcripts, etc.) Destructive remove_meeting_bot Remove a bot from a meeting Execute make_bot_speak Make a bot speak text during a meeting using text-to-speech Execute send_video_to_meeting Send a video to the meeting through the bot (Google Meet only) Write send_chat_message Send a chat message from the bot to the meeting Write send_image_to_meeting Send an image to the meeting through the bot (Google Meet only) Read get_bot_status Get the current status of a meeting bot Read get_chat_messages Get chat messages from the meeting

All 11 Attendee MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Attendee MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_meeting_bot

What does the create_meeting_bot tool do? +

Create a bot to join a meeting and record/transcribe it. It is categorised as a Execute tool in the Attendee MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_meeting_bot? +

Register the Attendee MCP Server MCP server in PolicyLayer and add a rule for create_meeting_bot: 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 Attendee MCP Server. Nothing to install.

What risk level is create_meeting_bot? +

create_meeting_bot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_meeting_bot? +

Yes. Add a rate_limit block to the create_meeting_bot 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.

How do I block create_meeting_bot completely? +

Set action: deny in the PolicyLayer policy for create_meeting_bot. 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.

What MCP server provides create_meeting_bot? +

create_meeting_bot is provided by the Attendee MCP Server MCP server (rexposadas/attendee-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Attendee MCP Server tool call.

Start from Attendee MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →