AI agents use remesh_create to create or update resources in Meshy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meshy environment.
This tool modifies/transforms existing 3D model data and creates new output in different formats, making it a Write operation rather than Read (which would be retrieval-only) or Destructive (which would be irreversible deletion). The blast radius is medium because while it creates/modifies data, these transformations are reversible—a remeshed model can be regenerated or the original retained.
From the tool's definition The tool description states it can 'remesh and export a 3D model' which involves modifying 3D model data and generating output files in various formats (glb, fbx, obj, usdz, blend, stl).
Attacks that exploit this kind of access
Remesh and export a 3D model into various formats (glb, fbx, obj, usdz, blend, stl). Provide either input_task_id or model_url. It is categorised as a Write tool in the Meshy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meshy MCP server in PolicyLayer and add a rule for remesh_create: 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 Meshy. Nothing to install.
remesh_create 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 remesh_create 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 remesh_create. 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.
remesh_create is provided by the Meshy MCP server (meshy-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →