get_slicer_profile

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-slicer-profile.md

WHAT IT DOES

What get_slicer_profile does on Kiln

AI agents call get_slicer_profile 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_slicer_profile is rated Low

The tool retrieves a slicer profile (settings/parameters used for 3D printing), which is a read operation with no side effects. Even if an AI agent misuses this by retrieving unintended profiles, the impact is limited to information disclosure about printer configurations.

From the tool's definition Tool name 'get_slicer_profile' indicates retrieval of a slicer configuration profile. The empty description limits certainty, but the 'get_' prefix strongly suggests a read-only query operation typical of configuration retrieval in 3D printer control systems.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_slicer_profile 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_slicer_profile, this is the rule to start with:

get_slicer_profile Allowed

get_slicer_profile 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_slicer_profile": {}
  }
}

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_slicer_profile call is checked against it from then on.

FAQ

Questions about get_slicer_profile

What does the get_slicer_profile tool do? +

get_slicer_profile 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_slicer_profile? +

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

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

Can I rate-limit get_slicer_profile? +

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

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

get_slicer_profile 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 →