Low Risk

stream_retexture_task

Stream updates for a retexture task.

How to control stream_retexture_task ↓

AI agents call stream_retexture_task to retrieve information from Meshy AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves status information about an ongoing retexture operation. Streaming task updates is a read-only operation that queries the state of a previously created task without modifying, deleting, or executing new operations.

From the tool's definition Tool name 'stream_retexture_task' and description 'Stream updates for a retexture task' indicates polling or subscribing to status/progress updates of an existing task.

Documented attack patterns abuse exactly the kind of access stream_retexture_task gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Meshy AI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stream_retexture_task:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "stream_retexture_task": {}
  }
}

stream_retexture_task is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Meshy AI MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the stream_retexture_task tool do? +

Stream updates for a retexture task. It is categorised as a Read tool in the Meshy AI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on stream_retexture_task? +

Register the Meshy AI MCP Server MCP server in PolicyLayer and add a rule for stream_retexture_task: 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 AI MCP Server. Nothing to install.

What risk level is stream_retexture_task? +

stream_retexture_task is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit stream_retexture_task? +

Yes. Add a rate_limit block to the stream_retexture_task 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.

How do I block stream_retexture_task completely? +

Set action: deny in the PolicyLayer policy for stream_retexture_task. 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.

What MCP server provides stream_retexture_task? +

stream_retexture_task is provided by the Meshy AI MCP Server MCP server (pasie15/meshy-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Meshy AI MCP Server tool call.

Deterministic rules across all 51 Meshy AI MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

51 Meshy AI MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.