bulc_set_current_level · BULC Building Designer MCP

WHAT IT DOES

What bulc_set_current_level does on BULC Building Designer

AI agents use bulc_set_current_level 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_set_current_level needs a policy

This tool changes application state (the active editing level) rather than querying it. State changes are write operations. However, the risk is low because: (1) the change is reversible (user can set a different level), (2) no data is created or deleted, (3) it only affects the context for future operations rather than data itself, and (4) misuse would simply cause subsequent edits to go to the wrong level, which…

From the tool's definition Tool description states it 'Set[s] which floor level is currently active for editing', which modifies the active state of the application.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bulc_set_current_level Rate-limited

bulc_set_current_level 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_set_current_level": {
      "limits": [
        {
          "counter": "bulc_set_current_level_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_set_current_level

What does the bulc_set_current_level tool do? +

Set which floor level is currently active for editing. New rooms/walls will be created on this level by default. 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_set_current_level? +

Register the BULC Building Designer MCP server in PolicyLayer and add a rule for bulc_set_current_level: 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_set_current_level? +

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

Can I rate-limit bulc_set_current_level? +

Yes. Add a rate_limit block to the bulc_set_current_level 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_set_current_level completely? +

Set action: deny in the PolicyLayer policy for bulc_set_current_level. 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_set_current_level? +

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