AI agents call retexture_list to retrieve information from Meshy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing retexture tasks without modifying, executing, or deleting any data. It is a straightforward read operation consistent with list/query patterns. Severity is low as listing tasks poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'retexture_list' and description 'List retexture tasks' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List retexture tasks. It is categorised as a Read tool in the Meshy MCP Server, which means it retrieves data without modifying state.
Register the Meshy MCP server in PolicyLayer and add a rule for retexture_list: 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.
retexture_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the retexture_list 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 retexture_list. 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.
retexture_list 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 →