create-my-calendar-permission

SERVERMs 365 SOURCE@jo3zik/ms-365-mcp-server

Medium RISK CLASS

Category Write

Parameters 41 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jo3zik-ms-365-mcp-server/create-my-calendar-permission.md

WHAT IT DOES

What create-my-calendar-permission does on Ms 365

AI agents use create-my-calendar-permission to create or update resources in Ms 365, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ms 365 environment.

Parameter	Type	Required	Description
`body`	object	Yes
`confirm`	boolean	—	For destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly app
`includeHeaders`	boolean	—	Include response headers (including ETag) in the response metadata
`excludeResponse`	boolean	—	Exclude the full response body and only return success or failure indication

Parameters from the server's own tool schema.

RISK

Why create-my-calendar-permission is rated Medium

An AI agent can call create-my-calendar-permission faster than any human can review: one bad instruction and it creates or modifies resources in Ms 365 by the hundred, each call as confident as the last.

Risk signalsAccepts raw HTML/template content (body) · High parameter count (12 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create-my-calendar-permission safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ms 365, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create-my-calendar-permission, this is the rule to start with:

create-my-calendar-permission Rate-limited

create-my-calendar-permission 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create-my-calendar-permission": {
      "limits": [
        {
          "counter": "create-my-calendar-permission_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ms 365, apply this rule, and every create-my-calendar-permission call is checked against it from then on.

FAQ

Questions about create-my-calendar-permission

What does the create-my-calendar-permission tool do? +

Create a calendarPermission resource to specify the identity and role of the user with whom the specified calendar is being shared or delegated. 💡 TIP: Shares the user's primary calendar with another user (or sets up a delegate). Body: { emailAddress: { name: 'Adele Vance', address: 'adele@contoso.com' }, role: 'read' | 'write' | 'delegateWithoutPrivateEventAccess' | 'delegateWithPrivateEventAccess', isInsideOrganization: true, isRemovable: true }. Use list-users to resolve the recipient SMTP. Returns the created calendarPermission with its id (used by update-my-calendar-permission and delete-my-calendar-permission). It is categorised as a Write tool in the Ms 365 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create-my-calendar-permission accept? +

create-my-calendar-permission accepts 4 parameters: body, confirm, includeHeaders, excludeResponse. Required: body. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create-my-calendar-permission? +

Register the Ms 365 MCP server in PolicyLayer and add a rule for create-my-calendar-permission: 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 Ms 365. Nothing to install.

What risk level is create-my-calendar-permission? +

create-my-calendar-permission is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create-my-calendar-permission? +

Yes. Add a rate_limit block to the create-my-calendar-permission 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.

How do I block create-my-calendar-permission completely? +

Set action: deny in the PolicyLayer policy for create-my-calendar-permission. 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.

What MCP server provides create-my-calendar-permission? +

create-my-calendar-permission is provided by the Ms 365 MCP server (@jo3zik/ms-365-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ms 365, and thousands of servers like it.

This server

All 194 Ms 365 tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →