Delete a vendor.
AI agents call delete_vendor to permanently remove resources in NGS360 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a vendor is a destructive operation that permanently removes vendor records from the NGS360 bioinformatics platform. This could have significant downstream effects on associated projects, workflows, and other platform entities that depend on vendor references. The operation cannot be undone through normal API operations, making it irreversibly destructive.
From the tool's definition Tool name is 'delete_vendor' and description states 'Delete a vendor.' The verb 'delete' combined with no mention of reversibility or undo capability indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a vendor. It is categorised as a Destructive tool in the NGS360 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the NGS360 MCP Server MCP server in PolicyLayer and add a rule for delete_vendor: 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 NGS360 MCP Server. Nothing to install.
delete_vendor 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 delete_vendor 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 delete_vendor. 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.
delete_vendor is provided by the NGS360 MCP Server MCP server (ngs360/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →