New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_instance_trigger

Delete a configured instance trigger. This removes its event history and connector sync ledger.

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/delete-instance-trigger.md

What delete_instance_trigger does on ProAgentStore

AI agents call delete_instance_trigger to permanently remove resources in ProAgentStore, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_instance_trigger is rated Critical

Irreversibly deletes configured triggers and their historical data without undo capability.

From the tool's definition Delete configured instance trigger, removes event history and connector sync ledger.

Questions about delete_instance_trigger

What does the delete_instance_trigger tool do? +

Delete a configured instance trigger. This removes its event history and connector sync ledger. It is categorised as a Destructive tool in the ProAgentStore MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_instance_trigger? +

Register the ProAgentStore MCP server in PolicyLayer and add a rule for delete_instance_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 ProAgentStore. Nothing to install.

What risk level is delete_instance_trigger? +

delete_instance_trigger is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_instance_trigger? +

Yes. Add a rate_limit block to the delete_instance_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.

How do I block delete_instance_trigger completely? +

Set action: deny in the PolicyLayer policy for delete_instance_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.

What MCP server provides delete_instance_trigger? +

delete_instance_trigger is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ProAgentStore, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ProAgentStore's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.