Apply a material (color and basic surface properties) to an existing object.
AI agents use blender_apply_material to create or update resources in Polybridge MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Polybridge MCP environment.
This tool performs a modification to Blender object properties (material application), which qualifies as Write rather than Execute or Destructive. While it changes object state, the change is reversible—materials can be removed or replaced.
From the tool's definition The tool description states it will 'Apply a material (color and basic surface properties) to an existing object.' This modifies the visual/material properties of an object in Blender, which is a reversible state change to data.
Attacks that exploit this kind of access
Apply a material (color and basic surface properties) to an existing object. It is categorised as a Write tool in the Polybridge MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Polybridge MCP server in PolicyLayer and add a rule for blender_apply_material: 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_apply_material is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the blender_apply_material 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_apply_material. 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_apply_material 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 →