Low Risk

get_door_operation_types

get_door_operation_types

How to control get_door_operation_types ↓

AI agents call get_door_operation_types to retrieve information from IFC Bonsai MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool retrieves or queries door operation type definitions with no apparent side effects on IFC models or data. It follows read-operation naming conventions ('get_') and fits the pattern of other reference/enumeration lookups that don't modify state. Empty description lowers confidence slightly but the name provides sufficient evidence of read semantics.

From the tool's definition Tool name 'get_door_operation_types' indicates retrieval of predefined door operation type information; empty description limits specificity but name suggests read-only query of static or reference data.

Documented attack patterns abuse exactly the kind of access get_door_operation_types 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 get_door_operation_types:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_door_operation_types": {}
  }
}

get_door_operation_types is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register IFC Bonsai MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_door_operation_types tool do? +

get_door_operation_types. It is categorised as a Read tool in the IFC Bonsai MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_door_operation_types? +

Register the IFC Bonsai MCP server in PolicyLayer and add a rule for get_door_operation_types: 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.

What risk level is get_door_operation_types? +

get_door_operation_types is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_door_operation_types? +

Yes. Add a rate_limit block to the get_door_operation_types 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.

How do I block get_door_operation_types completely? +

Set action: deny in the PolicyLayer policy for get_door_operation_types. 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.

What MCP server provides get_door_operation_types? +

get_door_operation_types 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.

Enforce policy on every IFC Bonsai MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.