Helper to create a recurring event with simplified inputs
AI agents use outlook_create_recurrence_helper to create or update resources in Outlook — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outlook environment.
Creating a recurring calendar event is a reversible write operation that adds new data to the calendar system. While it does not delete or irreversibly alter existing data (Destructive), does not involve financial transactions (Financial), or execute arbitrary code (Execute), it does create and persist new calendar entries.
From the tool's definition Tool name and description indicate it 'create a recurring event', which modifies calendar state by adding new data. The server description confirms this is part of Outlook calendar management capabilities.
Documented attack patterns abuse exactly the kind of access outlook_create_recurrence_helper gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Outlook, and nothing reaches the server without passing your rules. This is the rule we recommend for outlook_create_recurrence_helper:
{
"version": "1",
"default": "deny",
"tools": {
"outlook_create_recurrence_helper": {
"limits": [
{
"counter": "outlook_create_recurrence_helper_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}outlook_create_recurrence_helper stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Helper to create a recurring event with simplified inputs. It is categorised as a Write tool in the Outlook MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Outlook MCP server in PolicyLayer and add a rule for outlook_create_recurrence_helper: 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. Nothing to install.
outlook_create_recurrence_helper 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 outlook_create_recurrence_helper 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 outlook_create_recurrence_helper. 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.
outlook_create_recurrence_helper is provided by the Outlook MCP server (xenoxilus/outlook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Outlook, 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.
43 Outlook tools catalogued and risk-classified — across an index of 43,000+ MCP servers.