New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

force_print_oversize

A execute tool on the Kiln MCP server.

SERVERKiln SOURCEcodeofaxel/Kiln
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kiln/force-print-oversize.md

What force_print_oversize does on Kiln

AI agents invoke force_print_oversize to trigger actions in Kiln. 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 force_print_oversize is rated High

The name suggests forcing a print job to proceed despite being oversized, which could override safety limits on a 3D printer and potentially cause physical damage or failed prints. In the context of 3D printer control (OctoPrint, Moonraker, Bambu, Prusa, Elegoo), forcing an oversized print could damage hardware or waste materials. Classified as Execute due to triggering an external physical operation.

From the tool's definition Tool name 'force_print_oversize' — no description provided

Questions about force_print_oversize

What does the force_print_oversize tool do? +

force_print_oversize is a execute tool on the Kiln MCP server. It is categorised as a Execute tool in the Kiln MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on force_print_oversize? +

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

What risk level is force_print_oversize? +

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

Can I rate-limit force_print_oversize? +

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

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

force_print_oversize is provided by the Kiln MCP server (codeofaxel/Kiln). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Kiln, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Kiln's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.