remove_canned_service_part

Remove a part line item from a canned service template.

SERVERShopmonkey MCP Server SOURCEabbottdevelopments/shopmonkey-mcp-server
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/abbottdevelopments-shopmonkey-mcp-server/remove-canned-service-part.md

What remove_canned_service_part does on Shopmonkey MCP Server

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

Why remove_canned_service_part is rated Critical

The tool deletes a part line item from a canned service template, which is an irreversible operation that cannot be undone by simply re-adding the item (the deletion destroys the template record state).

From the tool's definition Tool name contains 'remove' and description states 'Remove a part line item from a canned service template' — this irreversibly deletes data from a template.

Questions about remove_canned_service_part

What does the remove_canned_service_part tool do? +

Remove a part line item from a canned service template. It is categorised as a Destructive tool in the Shopmonkey MCP Server 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 remove_canned_service_part? +

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

What risk level is remove_canned_service_part? +

remove_canned_service_part 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 remove_canned_service_part? +

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

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

remove_canned_service_part is provided by the Shopmonkey MCP Server MCP server (abbottdevelopments/shopmonkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Shopmonkey MCP Server, 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 Shopmonkey MCP Server'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.