remove_product_file
Remove the attached distributable file from a product.
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/remove-product-file.md
What remove_product_file does on Sequenzy Mcp
AI agents call remove_product_file to permanently remove resources in Sequenzy Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_product_file is rated Critical
Removing an attached file from a product is an irreversible deletion of associated data. The file attachment is permanently detached/removed, which cannot be undone. High severity because it could destroy product delivery assets affecting customers and revenue.
From the tool's definition Remove the attached distributable file from a product
Attacks that exploit this kind of access
The rule that runs remove_product_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sequenzy Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_product_file, this is the rule to start with:
remove_product_file 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 Sequenzy Mcp, apply this rule, and every remove_product_file call is checked against it from then on.
Questions about remove_product_file
Remove the attached distributable file from a product. It is categorised as a Destructive tool in the Sequenzy Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sequenzy MCP server in PolicyLayer and add a rule for remove_product_file: 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 Sequenzy Mcp. Nothing to install.
remove_product_file 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_product_file 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_product_file. 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_product_file is provided by the Sequenzy MCP server (Sequenzy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sequenzy, and thousands of servers like it.
Across the catalogue