List tasks across all task types with filtering and pagination. Queries one or all task types. When task_type is omitted, queries ALL 7 list-capable endpoints in parallel and merges results sorted by creation time. Args: - task_type (enum, optional): Filter by task type. If omitted, queries ALL t...
AI agents call meshy_list_tasks to retrieve information from Meshy 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 and filters existing task information without creating, modifying, deleting, or executing operations. It is a read-only query operation that returns data about tasks across the Meshy platform. The lack of write/execute/destructive capabilities and the explicit listing behavior clearly place it in the Read category with low severity.
From the tool's definition Tool description states it "List tasks" and "Queries" task types with "filtering and pagination". The function signature accepts optional parameters for filtering and returns merged results without modifying any data.
Documented attack patterns abuse exactly the kind of access meshy_list_tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meshy MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meshy_list_tasks:
{
"version": "1",
"default": "deny",
"tools": {
"meshy_list_tasks": {}
}
}meshy_list_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 tasks across all task types with filtering and pagination. Queries one or all task types. When task_type is omitted, queries ALL 7 list-capable endpoints in parallel and merges results sorted by creation time. Args: - task_type (enum, optional): Filter by task type. If omitted, queries ALL types and merges results. Supported:. It is categorised as a Read tool in the Meshy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meshy MCP Server MCP server in PolicyLayer and add a rule for meshy_list_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 MCP Server. Nothing to install.
meshy_list_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 meshy_list_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 meshy_list_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.
meshy_list_tasks is provided by the Meshy MCP Server MCP server (meshy-dev/meshy-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meshy MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Meshy MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.