Apply a material to an object
AI agents use apply_material to create or update resources in Threlte — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Threlte environment.
Applying a material modifies scene state but is reversible (a different material can be applied afterward). It does not execute arbitrary code, delete data, or cause financial impact. While it affects scene rendering, the blast radius is limited to visual presentation changes.
From the tool's definition Tool name 'apply_material' and description 'Apply a material to an object' indicate modification of object properties in a Three.js/Threlte scene. This is a reversible operation that changes visual rendering attributes.
Documented attack patterns abuse exactly the kind of access apply_material gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Threlte, and nothing reaches the server without passing your rules. This is the rule we recommend for apply_material:
{
"version": "1",
"default": "deny",
"tools": {
"apply_material": {
"limits": [
{
"counter": "apply_material_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}apply_material stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Apply a material to an object. It is categorised as a Write tool in the Threlte MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Threlte MCP server in PolicyLayer and add a rule for 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 Threlte. Nothing to install.
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 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 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.
apply_material is provided by the Threlte MCP server (serifeusstudio/threlte-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Threlte, 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.
30 Threlte tools catalogued and risk-classified — across an index of 43,000+ MCP servers.