AI agents call listAccounts to retrieve information from Outlook without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of email account information without altering data, executing code, or performing any side effects. It is a straightforward read operation that retrieves existing configuration data. Severity is low because account names and email addresses are generally non-sensitive metadata already known to the user in their own Outlook installation.
From the tool's definition Tool name 'listAccounts' and description 'List all configured email accounts' indicate retrieval of account metadata with no modification or execution.
Attacks that exploit this kind of access
List all configured email accounts in Outlook (name, email, type). It is categorised as a Read tool in the Outlook MCP Server, which means it retrieves data without modifying state.
Register the Outlook MCP server in PolicyLayer and add a rule for listAccounts: 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 Outlook. Nothing to install.
listAccounts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listAccounts 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 listAccounts. 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.
listAccounts is provided by the Outlook MCP server (lihaokun/outlook-mcp). 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 →