AI agents call get_user_view to retrieve information from Bonsai-mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming convention and peer tools that are clearly Read operations (all 'get_*' prefixed tools that retrieve IFC data), this tool most likely retrieves user view settings or configuration without modifying state. The empty description reduces confidence from high to moderate. No destructive, financial, or execute-like side effects are suggested by the name within a Blender/IFC modeling context.
From the tool's definition Tool name 'get_user_view' suggests retrieval of view/display settings or user preferences. Context of sibling tools (get_ifc_project_info, get_ifc_properties, get_ifc_georeferencing_info) indicates query-oriented operations. However, description is empty.
Documented attack patterns abuse exactly the kind of access get_user_view 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 get_user_view:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_view": {}
}
}get_user_view 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_user_view. It is categorised as a Read tool in the Bonsai-mcp MCP Server, which means it retrieves data without modifying state.
Register the Bonsai- MCP server in PolicyLayer and add a rule for get_user_view: 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.
get_user_view 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_user_view 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_user_view. 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_user_view 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.