Retrieve full details for a specific NA meeting by its BMLT meeting ID. Use this after bmlt_search_meetings to get the complete record for a specific meeting. Args: - meeting_id (number): The BMLT meeting ID (the
AI agents call bmlt_get_meeting_details to retrieve information from Bmlt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves existing data about NA meetings without modifying, creating, or deleting records. It is a lookup/fetch operation with no side effects, fitting the Read category. Severity is low because exposure of meeting location and schedule information carries minimal security risk in the context of public NA meeting directories.
From the tool's definition Tool name and description indicate retrieval of meeting details: 'Retrieve full details for a specific NA meeting by its BMLT meeting ID.' The args show a meeting_id parameter for lookup. No mutation, deletion, or side effects are described.
Attacks that exploit this kind of access
Retrieve full details for a specific NA meeting by its BMLT meeting ID. Use this after bmlt_search_meetings to get the complete record for a specific meeting. Args: - meeting_id (number): The BMLT meeting ID (the. It is categorised as a Read tool in the Bmlt MCP Server, which means it retrieves data without modifying state.
Register the Bmlt MCP server in PolicyLayer and add a rule for bmlt_get_meeting_details: 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 Bmlt. Nothing to install.
bmlt_get_meeting_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bmlt_get_meeting_details 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 bmlt_get_meeting_details. 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.
bmlt_get_meeting_details is provided by the Bmlt MCP server (jbonjour/bmlt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →