Browse 3D models in your workspace with filtering and pagination. This tool lists all completed models in your workspace. Only shows models with status SUCCEEDED. Args: - workspace_id (string, optional): Workspace ID (uses default workspace if omitted) - filter (enum): Filter by visibility -
AI agents call meshy_list_models 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 is a straightforward read operation that queries and retrieves a list of existing 3D models from a workspace with filtering and pagination. It has no side effects, cannot modify data, execute code, or delete resources. The blast radius of misuse is minimal—an agent could only gain visibility into available models.
From the tool's definition Tool description explicitly states it 'Browse 3D models' and 'lists all completed models'. The args include only optional workspace_id and filter parameters for visibility. No modification, deletion, or execution capabilities are present.
Documented attack patterns abuse exactly the kind of access meshy_list_models 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_models:
{
"version": "1",
"default": "deny",
"tools": {
"meshy_list_models": {}
}
} meshy_list_models 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.
Browse 3D models in your workspace with filtering and pagination. This tool lists all completed models in your workspace. Only shows models with status SUCCEEDED. Args: - workspace_id (string, optional): Workspace ID (uses default workspace if omitted) - filter (enum): Filter by visibility -. 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_models: 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_models 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_models 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_models. 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_models 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.