Place a furniture item at the specified position.
AI agents use bulc_place_furniture 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.
Placing furniture modifies the building design by adding a new object, making this a Write operation. The action is reversible (furniture can be removed or repositioned via undo or deletion), not destructive. The blast radius is low since misuse would only clutter the design without causing data loss or external system harm.
From the tool's definition Tool name 'bulc_place_furniture' and description 'Place a furniture item at the specified position' indicate creating/adding a furniture object to the building design.
Attacks that exploit this kind of access
Place a furniture item at the specified position. 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_place_furniture: 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_place_furniture 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_place_furniture 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_place_furniture. 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_place_furniture 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 →