bulc_run_evac · BULC Building Designer MCP: Risk & Policy

WHAT IT DOES

What bulc_run_evac does on BULC Building Designer

AI agents invoke bulc_run_evac 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.

WHY IT NEEDS A POLICY

Why bulc_run_evac needs a policy

This tool triggers execution of a complex external simulation (JuPedSim evacuation modeling) whose outcomes depend on the current building state and simulation parameters.

From the tool's definition Tool name 'bulc_run_evac' and description 'Start evacuation simulation using JuPedSim' indicate execution of an external simulation process with real-time effects on the building design environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bulc_run_evac Rate-limited

bulc_run_evac stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bulc_run_evac": {
      "limits": [
        {
          "counter": "bulc_run_evac_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches BULC Building Designer, so you can run agents against it safely.

FAQ

Questions about bulc_run_evac

What does the bulc_run_evac tool do? +

Start evacuation simulation using JuPedSim. 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.

How do I enforce a policy on bulc_run_evac? +

Register the BULC Building Designer MCP server in PolicyLayer and add a rule for bulc_run_evac: 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.

What risk level is bulc_run_evac? +

bulc_run_evac is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit bulc_run_evac? +

Yes. Add a rate_limit block to the bulc_run_evac 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.

How do I block bulc_run_evac completely? +

Set action: deny in the PolicyLayer policy for bulc_run_evac. 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.

What MCP server provides bulc_run_evac? +

bulc_run_evac 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.

// THE FULL RECORD

bulc_run_evac is one line of BULC Building Designer's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →