generate_prusaslicer_config · Prusa MCP: Risk & Policy

WHAT IT DOES

What generate_prusaslicer_config does on PrusaMCP

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

WHY IT NEEDS A POLICY

Why generate_prusaslicer_config needs a policy

This tool creates or generates a configuration file (.ini format) for PrusaSlicer. This is a Write operation as it produces new data artifacts that are stored and used by the slicer software. The severity is medium because while configuration files can affect 3D print behavior, they are reversible and do not cause irreversible data loss or execute arbitrary code.

From the tool's definition Tool name contains 'generate' and description states 'Génère un fichier .ini compatible PrusaSlicer' (generates a PrusaSlicer-compatible .ini file), indicating file creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_prusaslicer_config Rate-limited

generate_prusaslicer_config 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": {
    "generate_prusaslicer_config": {
      "limits": [
        {
          "counter": "generate_prusaslicer_config_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 PrusaMCP, so you can run agents against it safely.

FAQ

Questions about generate_prusaslicer_config

What does the generate_prusaslicer_config tool do? +

Génère un fichier .ini compatible PrusaSlicer à partir d. It is categorised as a Write tool in the PrusaMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_prusaslicer_config? +

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

What risk level is generate_prusaslicer_config? +

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

Can I rate-limit generate_prusaslicer_config? +

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

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

generate_prusaslicer_config is provided by the Prusa MCP server (noosbai/prusamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.