Retrieve metadata about a BMLT root server, including version and geographic center. Use this to verify a server is reachable, check its version, or get its default center coordinates. Args: - root_server_url (string, optional): BMLT root server URL. Defaults to
AI agents call bmlt_get_server_info 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 simple read-only query to obtain server metadata. It has no side effects, cannot modify data, execute code, delete resources, or create financial obligations. The blast radius of misuse is minimal—retrieving public server information poses negligible risk. Confidence is high due to explicit 'Retrieve' language and informative description.
From the tool's definition Tool description explicitly states 'Retrieve metadata about a BMLT root server, including version and geographic center.' Keywords: 'Retrieve', 'metadata', 'verify a server is reachable', 'check its version'.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Retrieve metadata about a BMLT root server, including version and geographic center. Use this to verify a server is reachable, check its version, or get its default center coordinates. 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_get_server_info: 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_server_info 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_server_info 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_server_info. 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_server_info 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 →