AI agents call get_calendars to retrieve information from Outlook Calendar MCP 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 calendar information without modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves metadata about available calendars. The local-only, privacy-focused nature of the server reduces risk further, as data does not leave the user's machine. No sensitive financial, destructive, or executable actions are involved.
From the tool's definition Tool name 'get_calendars' and description 'List available calendars' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_calendars gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Outlook Calendar MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_calendars:
{
"version": "1",
"default": "deny",
"tools": {
"get_calendars": {}
}
}get_calendars is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List available calendars. It is categorised as a Read tool in the Outlook Calendar MCP MCP Server, which means it retrieves data without modifying state.
Register the Outlook Calendar MCP server in PolicyLayer and add a rule for get_calendars: 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 Calendar MCP. Nothing to install.
get_calendars 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 get_calendars 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 get_calendars. 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.
get_calendars is provided by the Outlook Calendar MCP server (merajmehrabi/outlook_calendar_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Outlook Calendar MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Outlook Calendar MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.