remove_canned_service_subcontract
Remove a subcontract line item from a canned service template.
This record as markdown: /tools/abbottdevelopments-shopmonkey-mcp-server/remove-canned-service-subcontract.md
What remove_canned_service_subcontract does on Shopmonkey MCP Server
AI agents call remove_canned_service_subcontract 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_subcontract is rated Critical
This tool deletes a subcontract line item from a canned service template, which is an irreversible operation. Once removed, the line item cannot be recovered without manual intervention or API restoration. While the blast radius is limited to a single template item rather than the entire system, this is clearly a destructive action that permanently removes data.
From the tool's definition Tool name includes 'remove' and description states 'Remove a subcontract line item from a canned service template.' The verb 'remove' in the context of deleting line items from templates indicates irreversible deletion.
Attacks that exploit this kind of access
The rule that runs remove_canned_service_subcontract safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Shopmonkey MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_canned_service_subcontract, this is the rule to start with:
remove_canned_service_subcontract is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Shopmonkey MCP Server, apply this rule, and every remove_canned_service_subcontract call is checked against it from then on.
Questions about remove_canned_service_subcontract
Remove a subcontract 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.
Register the Shopmonkey MCP Server MCP server in PolicyLayer and add a rule for remove_canned_service_subcontract: 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.
remove_canned_service_subcontract is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_canned_service_subcontract 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 remove_canned_service_subcontract. 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.
remove_canned_service_subcontract 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.
Across the catalogue