Remove a local encryption profile.
AI agents call remove_encryption_profile to permanently remove resources in Todos — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing an encryption profile deletes security infrastructure irreversibly. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' High severity because loss of encryption profiles could lock users out of encrypted data, compromise security posture, or prevent access to previously protected information.
From the tool's definition Tool name 'remove_encryption_profile' explicitly uses 'remove', which indicates deletion. Description states it will 'Remove a local encryption profile' — this is an irreversible action that destroys encryption configuration data that cannot be recovered.
Attacks that exploit this kind of access
Remove a local encryption profile. It is categorised as a Destructive tool in the Todos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todos MCP server in PolicyLayer and add a rule for remove_encryption_profile: 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 Todos. Nothing to install.
remove_encryption_profile 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 remove_encryption_profile 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 remove_encryption_profile. 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.
remove_encryption_profile is provided by the Todos MCP server (@hasna/todos). 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 →