AI agents use place_ifc_object to create or update resources in Bonsai-mcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bonsai-mcp environment.
The name implies creating or modifying the position of an IFC object within a building model, which is a Write operation. Without a description, confidence is low, but 'place' typically means creating/positioning something rather than reading. Given sibling tools include execute_blender_code and various IFC manipulation tools, this likely modifies the model.
From the tool's definition Tool name 'place_ifc_object' suggests placing/positioning an object in the IFC model. Description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access place_ifc_object gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bonsai-mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for place_ifc_object:
{
"version": "1",
"default": "deny",
"tools": {
"place_ifc_object": {
"limits": [
{
"counter": "place_ifc_object_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}place_ifc_object 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.
Free to start. No card required.
place_ifc_object. It is categorised as a Write tool in the Bonsai-mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bonsai- MCP server in PolicyLayer and add a rule for place_ifc_object: 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 Bonsai-mcp. Nothing to install.
place_ifc_object 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 place_ifc_object 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 place_ifc_object. 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.
place_ifc_object is provided by the Bonsai- MCP server (jotaderodriguez/bonsai_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bonsai-mcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Bonsai-mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.