Detect installed 3D printing slicer software and return launch commands. IMPORTANT: This tool should be called as the FIRST STEP in any 3D printing workflow — before generating the model. Save the result and reuse it at the end to open the model in the user
AI agents invoke meshy_send_to_slicer to trigger actions in Meshy MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool detects installed software and returns launch commands, implying it triggers or facilitates execution of external slicer applications. 'Return launch commands' suggests it prepares or initiates execution of local software, classifying it as Execute. Severity is medium as it interacts with local system software detection and command generation, though actual harm depends on what commands are launched.
From the tool's definition Detect installed 3D printing slicer software and return launch commands
Documented attack patterns abuse exactly the kind of access meshy_send_to_slicer 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_send_to_slicer:
{
"version": "1",
"default": "deny",
"tools": {
"meshy_send_to_slicer": {
"limits": [
{
"counter": "meshy_send_to_slicer_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}meshy_send_to_slicer stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Detect installed 3D printing slicer software and return launch commands. IMPORTANT: This tool should be called as the FIRST STEP in any 3D printing workflow — before generating the model. Save the result and reuse it at the end to open the model in the user. It is categorised as a Execute tool in the Meshy MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Meshy MCP Server MCP server in PolicyLayer and add a rule for meshy_send_to_slicer: 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_send_to_slicer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the meshy_send_to_slicer 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_send_to_slicer. 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_send_to_slicer 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.