get_selected_ifc_entities

THE RISK

Low Risk

Why get_selected_ifc_entities needs a policy

This tool retrieves metadata about currently selected IFC entities in Blender. It performs no side effects, creates no data, executes no code, deletes nothing, and moves no money. The operation is purely informational — querying the state of selected objects and returning their corresponding IFC entity data.

From the tool's definition Tool description states 'Get IFC entities corresponding to the currently selected objects in Blender' — a retrieval operation with the verb 'Get' indicating data querying without modification.

Documented attack patterns abuse exactly the kind of access get_selected_ifc_entities gives an agent:

POLICY

How to control get_selected_ifc_entities

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 get_selected_ifc_entities:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_selected_ifc_entities": {}
  }
}

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

Create a free account and register Bonsai-mcp — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bonsai-mcp tools

Execute execute_blender_code Execute arbitrary Python code in Blender. Write georeference_ifc_model georeference_ifc_model Write place_ifc_object place_ifc_object Write export_bc3_budget export_bc3_budget Write export_drawing_png export_drawing_png Write export_ifc_data export_ifc_data Write generate_ids generate_ids Read get_ifc_georeferencing_info get_ifc_georeferencing_info

All 17 Bonsai-mcp tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_selected_ifc_entities

What does the get_selected_ifc_entities tool do? +

Get IFC entities corresponding to the currently selected objects in Blender. It is categorised as a Read tool in the Bonsai-mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_selected_ifc_entities? +

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

What risk level is get_selected_ifc_entities? +

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

Can I rate-limit get_selected_ifc_entities? +

Yes. Add a rate_limit block to the get_selected_ifc_entities 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_selected_ifc_entities completely? +

Set action: deny in the PolicyLayer policy for get_selected_ifc_entities. 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_selected_ifc_entities? +

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

Enforce policy on every Bonsai-mcp tool call.

Start from Bonsai-mcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →