Get detailed evacuation results including per-agent trajectories,
AI agents call bulc_get_evac_result to retrieve information from BULC Building Designer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves simulation data (evacuation results and trajectories) without modifying, deleting, or executing operations. It is a passive read operation on existing simulation outputs. No destructive, financial, or executable actions are implied. The low severity reflects minimal blast radius—misuse would only expose data, not alter building designs or trigger unwanted simulations.
From the tool's definition Tool name 'bulc_get_evac_result' and description 'Get detailed evacuation results' indicate a retrieval operation.
Attacks that exploit this kind of access
Get detailed evacuation results including per-agent trajectories,. It is categorised as a Read tool in the BULC Building Designer MCP Server, which means it retrieves data without modifying state.
Register the BULC Building Designer MCP server in PolicyLayer and add a rule for bulc_get_evac_result: 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 BULC Building Designer. Nothing to install.
bulc_get_evac_result 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 bulc_get_evac_result 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 bulc_get_evac_result. 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.
bulc_get_evac_result is provided by the BULC Building Designer MCP server (using76/bulc_mcp). 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 →