Delete provider.
AI agents call deactivate_provider to permanently remove resources in Terra Config MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible action (deletion) on provider configurations within the Terra ecosystem. Once a provider is deleted, the integration is removed and would require manual reconfiguration. This fits the Destructive category as it cannot be undone through normal tool operations.
From the tool's definition Tool name 'deactivate_provider' with description 'Delete provider' indicates irreversible removal of a provider configuration. Combined with sibling tool 'delete_destination' on the same server, this establishes a pattern of destructive operations.
Attacks that exploit this kind of access
Delete provider. It is categorised as a Destructive tool in the Terra Config MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Terra Config MCP Server MCP server in PolicyLayer and add a rule for deactivate_provider: 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 Terra Config MCP Server. Nothing to install.
deactivate_provider 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 deactivate_provider 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 deactivate_provider. 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.
deactivate_provider is provided by the Terra Config MCP Server MCP server (tryterra/terramcp). 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 →