process_model · Instant Meshes MCP: Risk & Policy

WHAT IT DOES

What process_model does on Instant Meshes

AI agents invoke process_model to trigger actions in Instant Meshes. 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.

WHY IT NEEDS A POLICY

Why process_model needs a policy

The tool name 'process_model' on a 3D processing server strongly implies it triggers external operations (running Instant Meshes, pymeshlab, or Blender) to transform 3D files. This falls under Execute as it runs external tools/processes. However, the description is empty, so confidence is reduced.

From the tool's definition Tool name 'process_model' on a server described as performing 'automated retopology, decimation, and quality analysis' integrating 'Instant Meshes, pymeshlab, and Blender 3.6'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

process_model Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "process_model": {
      "limits": [
        {
          "counter": "process_model_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Instant Meshes, so you can run agents against it safely.

FAQ

Questions about process_model

What does the process_model tool do? +

process_model. It is categorised as a Execute tool in the Instant Meshes MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on process_model? +

Register the Instant Meshes MCP server in PolicyLayer and add a rule for process_model: 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 Instant Meshes. Nothing to install.

What risk level is process_model? +

process_model is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit process_model? +

Yes. Add a rate_limit block to the process_model 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 process_model completely? +

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

process_model is provided by the Instant Meshes MCP server (lxy2109/instant-meshes-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.