Open the FDS result viewer window.
AI agents invoke bulc_open_result_viewer to trigger actions in BULC Building Designer. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation — opening a viewer window in the BULC/FDS fire simulation software. It doesn't merely read data passively; it executes a UI action that launches an application window, which is an external operation. Severity is medium as misuse could disrupt workflow but has limited destructive potential.
From the tool's definition Open the FDS result viewer window
Attacks that exploit this kind of access
Open the FDS result viewer window. It is categorised as a Execute tool in the BULC Building Designer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the BULC Building Designer MCP server in PolicyLayer and add a rule for bulc_open_result_viewer: 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_open_result_viewer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the bulc_open_result_viewer 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_open_result_viewer. 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_open_result_viewer 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 →