Stream updates for an animation task using server-sent events.
AI agents call stream_animation_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.
This tool retrieves real-time status information about an existing animation task via server-sent events. It has no side effects—it only queries and relays task progress data. While it is paired with task creation tools (create_animation_task, etc.) on the same server, this specific tool performs read-only monitoring of task state, placing it squarely in the Read category with low severity.
From the tool's definition Tool name contains 'stream' and description states it 'streams updates' for a task. The verb 'stream' combined with 'updates' indicates passive retrieval/monitoring of task status, not creation, modification, deletion, or execution of new operations.
Documented attack patterns abuse exactly the kind of access stream_animation_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_animation_task:
{
"version": "1",
"default": "deny",
"tools": {
"stream_animation_task": {}
}
}stream_animation_task is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Stream updates for an animation task using server-sent events. It is categorised as a Read tool in the Meshy AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meshy AI MCP Server MCP server in PolicyLayer and add a rule for stream_animation_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.
stream_animation_task 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 stream_animation_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.
Set action: deny in the PolicyLayer policy for stream_animation_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.
stream_animation_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.
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.