remove-account
Remove a Microsoft account from the cache. Accepts email address (e.g. user@outlook.com) or account ID. Use list-accounts to discover available accounts.
This record as markdown: /tools/jo3zik-ms-365-mcp-server/remove-account.md
What remove-account does on Ms 365
AI agents call remove-account to permanently remove resources in Ms 365, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
account | string | Yes | Email address or account ID of the account to remove |
Parameters from the server's own tool schema.
Why remove-account is rated Critical
Removing an account from the cache is a destructive operation that cannot be easily undone and eliminates access to that account's stored credentials/sessions. While the blast radius is somewhat limited to the local cache (not the actual Microsoft 365 account), the irreversible nature and potential for disrupting authenticated workflows justifies Destructive classification.
From the tool's definition Tool name 'remove-account' and description 'Remove a Microsoft account from the cache' explicitly indicate irreversible deletion of cached account data.
Attacks that exploit this kind of access
The rule that runs remove-account safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ms 365, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove-account, this is the rule to start with:
remove-account is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ms 365, apply this rule, and every remove-account call is checked against it from then on.
Questions about remove-account
Remove a Microsoft account from the cache. Accepts email address (e.g. user@outlook.com) or account ID. Use list-accounts to discover available accounts. It is categorised as a Destructive tool in the Ms 365 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove-account accepts 1 parameter: account. Required: account. The full parameter table on this page comes from the server's own tool schema.
Register the Ms 365 MCP server in PolicyLayer and add a rule for remove-account: 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 Ms 365. Nothing to install.
remove-account 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-account 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-account. 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-account is provided by the Ms 365 MCP server (@jo3zik/ms-365-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ms 365, and thousands of servers like it.
Across the catalogue