Configure a furniture item as an FDS fire source.
AI agents use bulc_set_fds_fire_source 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.
This tool modifies/configures an existing furniture item by setting it as a fire source in the FDS simulation. It is a reversible configuration change (write operation) rather than executing a simulation or destructively removing data. The severity is medium because misconfiguring fire source parameters could corrupt simulation setups, but the action itself is a targeted write to a simulation object.
From the tool's definition Configure a furniture item as an FDS fire source
Attacks that exploit this kind of access
Configure a furniture item as an FDS fire source. 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.
Register the BULC Building Designer MCP server in PolicyLayer and add a rule for bulc_set_fds_fire_source: 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_set_fds_fire_source is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bulc_set_fds_fire_source 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_set_fds_fire_source. 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_set_fds_fire_source 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 →