Search for Narcotics Anonymous meetings in the BMLT database. Returns a list of meetings matching the given filters. All filters are optional — omitting them returns all meetings for the default service body. Args: - root_server_url (string, optional): BMLT root server URL. Defaults to
AI agents call bmlt_search_meetings 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 performs a query operation that retrieves meeting data from a BMLT database based on optional filter parameters. It has no side effects—it only fetches and returns information. The blast radius of misuse is minimal; an agent could only retrieve publicly available meeting information, which poses no security, financial, or operational risk.
From the tool's definition Tool name is 'bmlt_search_meetings' and description states it 'Search for Narcotics Anonymous meetings' and 'Returns a list of meetings matching the given filters.' The description emphasizes filtering and retrieval with no mention of modification, deletion,…
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Search for Narcotics Anonymous meetings in the BMLT database. Returns a list of meetings matching the given filters. All filters are optional — omitting them returns all meetings for the default service body. Args: - root_server_url (string, optional): BMLT root server URL. Defaults to. 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_search_meetings: 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_search_meetings 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_search_meetings 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_search_meetings. 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_search_meetings 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 →