Process a textured 3D model for multi-color 3D printing. Cost: 10 credits. Segments the model
AI agents use meshy_process_multicolor to commit financial operations through Meshy MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Every invocation of this tool deducts 10 credits from the user's account balance, making it a financial commitment. While the primary action is processing/transforming a 3D model (Execute/Write), the mandatory credit cost elevates it to Financial as the most severe applicable category. Misuse by an AI agent could drain account credits rapidly.
From the tool's definition Cost: 10 credits — the tool consumes credits (a financial/quota resource) each time it is invoked.
Documented attack patterns abuse exactly the kind of access meshy_process_multicolor 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_process_multicolor:
{
"version": "1",
"default": "deny",
"tools": {
"meshy_process_multicolor": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to meshy_process_multicolor is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Process a textured 3D model for multi-color 3D printing. Cost: 10 credits. Segments the model. It is categorised as a Financial tool in the Meshy MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Meshy MCP Server MCP server in PolicyLayer and add a rule for meshy_process_multicolor: 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_process_multicolor is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the meshy_process_multicolor 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_process_multicolor. 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_process_multicolor 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.