Modify an existing FDS mesh. Change dimensions, cell counts, or other properties.
AI agents use bulc_modify_mesh 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.
The tool modifies existing mesh configuration (dimensions, cell counts, properties) but does not permanently delete or destroy data. Changes to mesh parameters in a simulation can typically be undone via the undo/redo support mentioned in the server description. This is a Write operation rather than Destructive.
From the tool's definition Tool name 'bulc_modify_mesh' and description 'Modify an existing FDS mesh. Change dimensions, cell counts, or other properties.' indicate reversible modification of mesh properties in a fire simulation model.
Attacks that exploit this kind of access
Modify an existing FDS mesh. Change dimensions, cell counts, or other properties. 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_modify_mesh: 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_modify_mesh 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_modify_mesh 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_modify_mesh. 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_modify_mesh 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 →