Rename an object in the scene
AI agents use rename_entity 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.
Renaming an entity is a reversible modification operation—the object itself remains intact and the change can be undone by renaming it again. This fits the Write category (creates or modifies data reversibly). The severity is low because renaming has minimal blast radius; it affects only metadata and does not impact functionality, financial state, or system integrity.
From the tool's definition Tool description states it can 'Rename an object in the scene', which modifies metadata about an existing entity without creating, deleting, or irreversibly altering its core data or state.
Documented attack patterns abuse exactly the kind of access rename_entity 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 rename_entity:
{
"version": "1",
"default": "deny",
"tools": {
"rename_entity": {
"limits": [
{
"counter": "rename_entity_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_entity 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.
Rename an object in the scene. 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 rename_entity: 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.
rename_entity 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 rename_entity 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 rename_entity. 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.
rename_entity 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.