AI agents invoke execute_ifc_code_tool to trigger actions in IFC Bonsai MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The verb 'execute' combined with 'code_tool' indicates this tool runs code, making it an Execute category tool. Without description details, confidence is slightly reduced, but the naming is unambiguous. Severity is high because code execution in a 3D modeling context could modify IFC structures unpredictably, corrupt model data, or affect the Blender environment depending on what code is supplied.
From the tool's definition Tool name 'execute_ifc_code_tool' explicitly indicates code execution capability. Description is empty, but the name combined with context (MCP server for IFC model manipulation in Blender) strongly suggests this tool runs arbitrary code against IFC models.
Documented attack patterns abuse exactly the kind of access execute_ifc_code_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and IFC Bonsai MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_ifc_code_tool:
{
"version": "1",
"default": "deny",
"tools": {
"execute_ifc_code_tool": {
"limits": [
{
"counter": "execute_ifc_code_tool_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_ifc_code_tool stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
execute_ifc_code_tool. It is categorised as a Execute tool in the IFC Bonsai MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the IFC Bonsai MCP server in PolicyLayer and add a rule for execute_ifc_code_tool: 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 IFC Bonsai MCP. Nothing to install.
execute_ifc_code_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_ifc_code_tool 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 execute_ifc_code_tool. 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.
execute_ifc_code_tool is provided by the IFC Bonsai MCP server (show2instruct/ifc-bonsai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 52 IFC Bonsai MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
52 IFC Bonsai MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.