Optimize a GLTF/GLB file with mesh simplification and texture compression
AI agents use optimize_gltf 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.
The tool modifies an existing GLTF/GLB file through mesh simplification and texture compression. These are transformations that alter the file's content but are reversible (the original can be re-optimized or restored from backup). This qualifies as Write rather than Destructive because optimization is not an irreversible deletion or permanent overwrite—users typically retain the source asset.
From the tool's definition optimize_gltf: 'Optimize a GLTF/GLB file with mesh simplification and texture compression' — the tool modifies the file by applying simplification and compression transformations.
Documented attack patterns abuse exactly the kind of access optimize_gltf 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 optimize_gltf:
{
"version": "1",
"default": "deny",
"tools": {
"optimize_gltf": {
"limits": [
{
"counter": "optimize_gltf_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}optimize_gltf 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.
Optimize a GLTF/GLB file with mesh simplification and texture compression. 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 optimize_gltf: 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.
optimize_gltf 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 optimize_gltf 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 optimize_gltf. 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.
optimize_gltf 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.