Redo the last undone operation. Returns information about what was redone.
AI agents use bulc_redo 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 redo operation modifies the design state by reapplying a previously undone change (e.g., re-creating a room or wall that was undone). While the operation itself is reversible via undo, it is a Write action that alters the building model. It is not Execute because it does not run arbitrary code or trigger external operations—it operates within the undo/redo stack.
From the tool's definition Tool name 'bulc_redo' and description 'Redo the last undone operation' indicate it reverses an undo action, thereby reapplying a previous modification to the building design.
Attacks that exploit this kind of access
Redo the last undone operation. Returns information about what was redone. 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_redo: 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_redo 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_redo 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_redo. 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_redo 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 →