Low Risk

list_remesh_tasks

List previously created remesh tasks. sort_by accepts

How to control list_remesh_tasks ↓

AI agents call list_remesh_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.

Low Risk

This tool queries and retrieves existing remesh task records. It is a read-only operation that does not create, modify, delete, or execute any operations. The lack of destructive or execute-like capabilities, combined with its passive information retrieval nature, classifies it as Read with low severity.

From the tool's definition Tool name 'list_remesh_tasks' and description 'List previously created remesh tasks' indicate retrieval of historical task data with no modification or side effects.

Documented attack patterns abuse exactly the kind of access list_remesh_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_remesh_tasks:

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

list_remesh_tasks 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 list_remesh_tasks tool do? +

List previously created remesh 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.

How do I enforce a policy on list_remesh_tasks? +

Register the Meshy AI MCP Server MCP server in PolicyLayer and add a rule for list_remesh_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.

What risk level is list_remesh_tasks? +

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

Can I rate-limit list_remesh_tasks? +

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

How do I block list_remesh_tasks completely? +

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

What MCP server provides list_remesh_tasks? +

list_remesh_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.

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.