Lists upcoming events from your calendar
AI agents call list-events 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 queries and retrieves calendar event information without side effects. It falls squarely into the Read category as it performs a passive data retrieval operation. The severity is low because calendar event metadata poses minimal risk even if exposed to an AI agent—it contains scheduling information but no financial data, destructive capabilities, or code execution potential.
From the tool's definition Tool name 'list-events' and description 'Lists upcoming events from your calendar' indicate retrieval of calendar data with no modification, creation, deletion, or execution of external operations.
Attacks that exploit this kind of access
Lists upcoming events from your calendar. 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-events: 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-events 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-events 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-events. 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-events 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 →