AI agents call delete_list_item to permanently remove resources in Freshdesk — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs irreversible deletion of data from a SharePoint list. This meets the definition of Destructive category as it cannot be undone. Severity is high due to potential data loss impact, though the blast radius is limited to individual list items rather than entire systems. High confidence due to explicit 'delete' terminology and clear destructive semantics.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete an item from a SharePoint list.' The action is irreversible data removal.
Documented attack patterns abuse exactly the kind of access delete_list_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Freshdesk, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_list_item:
{
"version": "1",
"default": "deny",
"hide": [
"delete_list_item"
]
}delete_list_item disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an item from a SharePoint list. It is categorised as a Destructive tool in the Freshdesk MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Freshdesk MCP server in PolicyLayer and add a rule for delete_list_item: 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 Freshdesk. Nothing to install.
delete_list_item 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_list_item 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_list_item. 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_list_item is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Freshdesk, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
422 Freshdesk tools catalogued and risk-classified — across an index of 43,000+ MCP servers.