Run ASET (Available Safe Egress Time) analysis at a specified exit location.
AI agents invoke bulc_run_aset_analysis 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.
ASET analysis is a fire safety simulation that runs complex calculations on the building model. While not immediately destructive or financial, it executes external operations whose outputs and side effects depend on user-supplied parameters (exit location).
From the tool's definition Tool performs 'Run ASET (Available Safe Egress Time) analysis' which triggers external simulation and computational operations on the BULC fire simulation software.
Attacks that exploit this kind of access
Run ASET (Available Safe Egress Time) analysis at a specified exit location. 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_run_aset_analysis: 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_run_aset_analysis 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_run_aset_analysis 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_run_aset_analysis. 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_run_aset_analysis 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 →