Retrieve all service bodies (NA regions, areas, districts) from a BMLT root server. Service bodies are the organizational units that manage meeting data in BMLT. Knowing the ID of a service body lets you filter meeting searches to a specific area. Use this to: - Discover service body IDs for use ...
AI agents call bmlt_get_service_bodies 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 retrieves organizational metadata (NA regions, areas, districts) from a BMLT root server without side effects. It is purely informational, supporting downstream meeting searches. It does not create, modify, delete, or execute arbitrary operations. Misuse by an AI agent would be limited to information gathering with no adverse impact.
From the tool's definition Tool description explicitly states 'Retrieve all service bodies' and use cases are limited to discovery and querying: 'Discover service body IDs', 'See the hierarchy', 'Find a specific area'.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Retrieve all service bodies (NA regions, areas, districts) from a BMLT root server. Service bodies are the organizational units that manage meeting data in BMLT. Knowing the ID of a service body lets you filter meeting searches to a specific area. Use this to: - Discover service body IDs for use in bmlt_search_meetings - See the hierarchy of areas served by a root server - Find a specific area. 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_service_bodies: 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_service_bodies 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_service_bodies 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_service_bodies. 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_service_bodies 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 →