AI agents use calendar_propose_new_time to create or update resources in M365 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your M365 environment.
Based on the tool name, this likely sends a counter-proposal for a new meeting time to calendar event participants, which is a write/modify action on calendar data. However, the empty description significantly lowers confidence. It could also trigger notifications to other users, making it closer to Execute, but Write is most probable given the naming convention and sibling tools context.
From the tool's definition Tool name 'calendar_propose_new_time' suggests modifying or responding to a calendar event by proposing a new meeting time. Description is empty and uninformative.
Attacks that exploit this kind of access
calendar_propose_new_time. It is categorised as a Write tool in the M365 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the M365 MCP server in PolicyLayer and add a rule for calendar_propose_new_time: 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 M365. Nothing to install.
calendar_propose_new_time is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the calendar_propose_new_time 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_propose_new_time. 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_propose_new_time is provided by the M365 MCP server (robin-collins/m365-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 →