Modify an existing object in the Blender scene. Parameters: - name: Name of the object to modify - location: Optional [x, y, z] location coordinates - rotation: Optional [x, y, z] rotation in radians - scale: Optional [x, y, z] scale factors - visible: Optional boolean to set visibility
AI agents use modify_object to create or update resources in Tripo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tripo MCP Server environment.
This is a Write operation because it creates or modifies data reversibly—transformations can be undone in Blender. It does not delete objects (Destructive), execute arbitrary code (Execute), or alter financial state. The medium severity reflects that misuse could corrupt a 3D scene or artistic work, but changes are non-destructive and recoverable.
From the tool's definition Tool modifies object properties (location, rotation, scale, visibility) in a Blender scene reversibly. The description states 'Modify an existing object' with parameters for transforming geometric and visibility attributes.
Documented attack patterns abuse exactly the kind of access modify_object gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tripo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for modify_object:
{
"version": "1",
"default": "deny",
"tools": {
"modify_object": {
"limits": [
{
"counter": "modify_object_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}modify_object 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.
Modify an existing object in the Blender scene. Parameters: - name: Name of the object to modify - location: Optional [x, y, z] location coordinates - rotation: Optional [x, y, z] rotation in radians - scale: Optional [x, y, z] scale factors - visible: Optional boolean to set visibility. It is categorised as a Write tool in the Tripo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tripo MCP Server MCP server in PolicyLayer and add a rule for modify_object: 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 Tripo MCP Server. Nothing to install.
modify_object 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 modify_object 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 modify_object. 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.
modify_object is provided by the Tripo MCP Server MCP server (vast-ai-research/tripo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Tripo MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Tripo MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.