List previously created rigging tasks. sort_by accepts
AI agents call list_rigging_tasks 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 or queries historical rigging task records. It is a read-only operation with no destructive, reversible, executable, or financial impact. The blast radius of misuse is minimal—an agent could view task history but cannot create, modify, delete, or execute tasks. Confidence is high despite incomplete description because the name and 'list' verb clearly indicate a read operation.
From the tool's definition Tool name 'list_rigging_tasks' and description 'List previously created rigging tasks' indicate a retrieval operation that queries existing data without modification or side effects.
Documented attack patterns abuse exactly the kind of access list_rigging_tasks 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 list_rigging_tasks:
{
"version": "1",
"default": "deny",
"tools": {
"list_rigging_tasks": {}
}
}list_rigging_tasks 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.
List previously created rigging tasks. sort_by accepts. 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 list_rigging_tasks: 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.
list_rigging_tasks 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 list_rigging_tasks 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 list_rigging_tasks. 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.
list_rigging_tasks 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.