get_model_print_history

A read tool on the Kiln MCP server.

SERVERKiln SOURCEcodeofaxel/Kiln

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kiln/get-model-print-history.md

WHAT IT DOES

What get_model_print_history does on Kiln

AI agents call get_model_print_history to retrieve information from Kiln without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_model_print_history is rated Low

This tool retrieves historical print data from a 3D printer system. It has no side effects, does not modify state, and does not trigger physical actions. Even if an AI agent misuses it by querying print history inappropriately, the blast radius is minimal—it only exposes non-destructive historical metadata. The low severity reflects that unauthorized access to print logs poses minimal operational or safety risk.

From the tool's definition Tool name 'get_model_print_history' uses the verb 'get', which indicates data retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_model_print_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Kiln, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_model_print_history, this is the rule to start with:

get_model_print_history Allowed

get_model_print_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_model_print_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every get_model_print_history call is checked against it from then on.

FAQ

Questions about get_model_print_history

What does the get_model_print_history tool do? +

get_model_print_history is a read tool on the Kiln MCP server. It is categorised as a Read tool in the Kiln MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_model_print_history? +

Register the Kiln MCP server in PolicyLayer and add a rule for get_model_print_history: 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 get_model_print_history? +

get_model_print_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_model_print_history? +

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

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

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

KEEP EXPLORING

More on Kiln, and thousands of servers like it.

This server

All 402 Kiln tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →