Return a list of all objects currently in the Blender scene.
AI agents call blender_list_objects to retrieve information from Polybridge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only operation—listing objects in a Blender scene. It does not modify, execute, delete, or create any data. The blast radius of misuse is minimal; an agent cannot cause damage by listing objects. This is a straightforward information retrieval operation.
From the tool's definition Tool name: 'blender_list_objects'; description: 'Return a list of all objects currently in the Blender scene.' This is a query operation that retrieves scene data without modification.
Attacks that exploit this kind of access
Return a list of all objects currently in the Blender scene. It is categorised as a Read tool in the Polybridge MCP MCP Server, which means it retrieves data without modifying state.
Register the Polybridge MCP server in PolicyLayer and add a rule for blender_list_objects: 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 Polybridge MCP. Nothing to install.
blender_list_objects 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 blender_list_objects 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 blender_list_objects. 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.
blender_list_objects is provided by the Polybridge MCP server (madjeek-web/polybridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →