bulc_save_evac_result · BULC Building Designer MCP

WHAT IT DOES

What bulc_save_evac_result does on BULC Building Designer

AI agents use bulc_save_evac_result to create or update resources in BULC Building Designer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BULC Building Designer environment.

WHY IT NEEDS A POLICY

Why bulc_save_evac_result needs a policy

This tool creates or persists data (evacuation simulation results) to disk in a .evac file. It is reversible—the file can be deleted or overwritten—so it does not qualify as Destructive. It is not executing arbitrary code or running simulations (that would be Execute); it is saving already-computed results. The Write category is appropriate for this data persistence operation.

From the tool's definition Tool name contains 'save' and description states 'Save current evacuation results to a .evac file', indicating creation/persistence of data in a file format.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bulc_save_evac_result Rate-limited

bulc_save_evac_result stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_save_evac_result": {
      "limits": [
        {
          "counter": "bulc_save_evac_result_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_save_evac_result

What does the bulc_save_evac_result tool do? +

Save current evacuation results to a .evac file. It is categorised as a Write tool in the BULC Building Designer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bulc_save_evac_result? +

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

What risk level is bulc_save_evac_result? +

bulc_save_evac_result is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bulc_save_evac_result? +

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

How do I block bulc_save_evac_result completely? +

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

What MCP server provides bulc_save_evac_result? +

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