delete_trigger
AI agents call delete_trigger to permanently remove resources in Fuul MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete_' prefix indicates an irreversible data removal operation. While the description is empty (lowering confidence slightly), the tool operates within a financial incentive system (sibling tools include 'approve_payouts', 'create_incentive', 'create_trigger'), making unintended deletion of triggers a high-blast-radius risk—triggers may gate payouts or disable fraud controls.
From the tool's definition Tool name 'delete_trigger' performs a deletion operation. In context of affiliate program management (where triggers govern payouts, incentives, and referral events), deletion of a trigger irreversibly removes a configuration that controls financial incentive…
Attacks that exploit this kind of access
delete_trigger. It is categorised as a Destructive tool in the Fuul MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fuul MCP Server MCP server in PolicyLayer and add a rule for delete_trigger: 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 Fuul MCP Server. Nothing to install.
delete_trigger 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_trigger 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_trigger. 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_trigger is provided by the Fuul MCP Server MCP server (kuyen-labs/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 →