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

delete_shipping_profile

Delete a saved local shipping profile.

SERVERKiln SOURCEcodeofaxel/Kiln
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kiln/delete-shipping-profile.md

What delete_shipping_profile does on Kiln

AI agents call delete_shipping_profile to permanently remove resources in Kiln, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_shipping_profile is rated Critical

The tool permanently removes a shipping profile, which cannot be undone. While the impact is scoped to a local configuration file (not critical system data), deletion is irreversible and represents loss of user-configured state. Severity is medium rather than high because the blast radius is limited to a single profile in a 3D printer management context, not financial transactions or multi-user systems.

From the tool's definition Tool name contains 'delete' and description states 'Delete a saved local shipping profile' — irreversible removal of stored data.

Questions about delete_shipping_profile

What does the delete_shipping_profile tool do? +

Delete a saved local shipping profile. It is categorised as a Destructive tool in the Kiln MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_shipping_profile? +

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

delete_shipping_profile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_shipping_profile? +

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

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

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

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.