Batch delete multiple intents.
AI agents call batch_delete_intents to permanently remove resources in Dialogflow CX MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call batch_delete_intents doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Dialogflow CX MCP Server is gone — there is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Batch delete multiple intents. It is categorised as a Destructive tool in the Dialogflow CX MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dialogflow CX MCP Server MCP server in PolicyLayer and add a rule for batch_delete_intents: 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 Dialogflow CX MCP Server. Nothing to install.
batch_delete_intents 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 batch_delete_intents 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 batch_delete_intents. 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.
batch_delete_intents is provided by the Dialogflow CX MCP Server MCP server (yash-kavaiya/conversation_agents_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.