List events on this identity
AI agents call calendar_list to retrieve information from Mailgent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and lists calendar events associated with an identity. This is a read-only operation with no capability to modify, delete, or execute actions. While calendar data may contain sensitive information (timing of meetings, attendees), the blast radius of misuse is limited to information disclosure. Severity is low because listing events does not enable destructive, financial, or execution-based harm.
From the tool's definition Tool name is 'calendar_list' and description states 'List events on this identity' — this is a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
List events on this identity. It is categorised as a Read tool in the Mailgent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mailgent MCP Server MCP server in PolicyLayer and add a rule for calendar_list: 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 Mailgent MCP Server. Nothing to install.
calendar_list 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 calendar_list 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 calendar_list. 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.
calendar_list is provided by the Mailgent MCP Server MCP server (loomal-ai/loomal-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 →