Lists contacts from a mailbox
AI agents call list-contacts to retrieve information from Outlook MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves contact data without creating, modifying, deleting, or executing any operations. It is a straightforward query operation that returns existing contact information. The severity is low because contact listings, while potentially sensitive, do not expose critical data like email credentials and are limited to contact metadata accessible to the authenticated user within their own mailbox context.
From the tool's definition Tool name is 'list-contacts' and description states 'Lists contacts from a mailbox'. The verb 'list' is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Lists contacts from a mailbox. It is categorised as a Read tool in the Outlook MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Outlook MCP Server MCP server in PolicyLayer and add a rule for list-contacts: 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 MCP Server. Nothing to install.
list-contacts 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 list-contacts 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 list-contacts. 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.
list-contacts is provided by the Outlook MCP Server MCP server (peacockery-studio/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 →