create_preset · QIDI Studio MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_preset does on QIDI Studio MCP Server

AI agents use create_preset to create or update resources in QIDI Studio MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QIDI Studio MCP Server environment.

WHY IT NEEDS A POLICY

Why create_preset needs a policy

This tool creates new presets reversibly—they can be modified or deleted later (evidenced by sibling tools like delete_preset and clone_preset). It is Write category (creates data) rather than Destructive. Severity is medium because misconfigured presets could cause print failures or hardware issues, but no data is permanently lost and physical damage is mitigated by hardware limits on the printer itself.

From the tool's definition Tool name 'create_preset' combined with server description stating it 'enables AI assistants to read and write filament, process, and machine presets'. The tool creates new 3D printing configuration presets.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_preset Rate-limited

create_preset stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_preset": {
      "limits": [
        {
          "counter": "create_preset_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about create_preset

What does the create_preset tool do? +

create_preset. It is categorised as a Write tool in the QIDI Studio MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_preset? +

Register the QIDI Studio MCP Server MCP server in PolicyLayer and add a rule for create_preset: 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 QIDI Studio MCP Server. Nothing to install.

What risk level is create_preset? +

create_preset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_preset? +

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

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

create_preset is provided by the QIDI Studio MCP Server MCP server (vladyankovenko/qidi-studio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.