Generate a Threlte/Svelte component from a GLTF/GLB file
AI agents use export_to_svelte 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 creates new source code artifacts (Svelte components) based on input files. While it doesn't delete data (ruling out Destructive) or execute arbitrary code on the system (ruling out Execute), it does produce new data that would be written to the developer's codebase. The severity is medium because generated code could have issues, but the developer retains review control before integration.
From the tool's definition Tool generates a new Threlte/Svelte component from a GLTF/GLB file, creating new code/data through the 'Generate' action. This is code generation and file creation, both Write operations.
Documented attack patterns abuse exactly the kind of access export_to_svelte 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 export_to_svelte:
{
"version": "1",
"default": "deny",
"tools": {
"export_to_svelte": {
"limits": [
{
"counter": "export_to_svelte_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} export_to_svelte 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.
Generate a Threlte/Svelte component from a GLTF/GLB file. 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 export_to_svelte: 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.
export_to_svelte 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 export_to_svelte 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 export_to_svelte. 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.
export_to_svelte 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.