This record as markdown: /tools/kiln/list-shipping-profiles.md
What list_shipping_profiles does on Kiln
AI agents call list_shipping_profiles 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.
Why list_shipping_profiles is rated Low
This tool retrieves and displays existing shipping profile data without modifying, deleting, or executing any operations. It is a simple data retrieval function. The blast radius of misuse is minimal—an agent could only enumerate shipping profiles, which poses no security or operational risk to the 3D printer systems.
From the tool's definition Tool name is 'list_shipping_profiles' with description 'List saved local shipping profiles.' The verb 'list' and action of retrieving saved profiles indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_shipping_profiles 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 list_shipping_profiles, this is the rule to start with:
list_shipping_profiles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every list_shipping_profiles call is checked against it from then on.
Questions about list_shipping_profiles
List saved local shipping profiles. It is categorised as a Read tool in the Kiln MCP Server, which means it retrieves data without modifying state.
Register the Kiln MCP server in PolicyLayer and add a rule for list_shipping_profiles: 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.
list_shipping_profiles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_shipping_profiles 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.
Set action: deny in the PolicyLayer policy for list_shipping_profiles. 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.
list_shipping_profiles 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.
This server
Across the catalogue