AI agents call get_scene_info 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.
The tool appears designed to read or fetch information about the current Blender scene (geometry, objects, properties, etc.). No evidence suggests it creates, modifies, deletes, executes code, or moves money. The empty description reduces confidence slightly, but the Read category is most consistent with a 'get_*' operation in a visualization/modeling tool context.
From the tool's definition Tool name 'get_scene_info' indicates a query/retrieval operation. The empty description prevents confirmation of specific behavior, but the naming convention and context within an IFC/Blender modeling server strongly suggests it retrieves scene metadata or…
Documented attack patterns abuse exactly the kind of access get_scene_info 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_scene_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_scene_info": {}
}
}get_scene_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_scene_info. It is categorised as a Read tool in the IFC Bonsai MCP MCP Server, which means it retrieves data without modifying state.
Register the IFC Bonsai MCP server in PolicyLayer and add a rule for get_scene_info: 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.
get_scene_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_scene_info 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 get_scene_info. 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.
get_scene_info 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.