Make this identity
AI agents use calendar_set_public to create or update resources in Mailgent MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mailgent MCP Server environment.
The tool appears to change calendar access controls (set to public), which is a reversible modification of settings/metadata. This is a Write action rather than Read (retrieves data) or Execute (runs code). Severity is medium because misconfiguration could expose personal schedule information to unintended audiences, but the change is reversible.
From the tool's definition Tool name 'calendar_set_public' suggests modifying calendar visibility/sharing settings. Description is incomplete ('Make this identity') but context indicates write operations on calendar configurations.
Attacks that exploit this kind of access
Make this identity. It is categorised as a Write tool in the Mailgent MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mailgent MCP Server MCP server in PolicyLayer and add a rule for calendar_set_public: 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_set_public 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_set_public 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_set_public. 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_set_public 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 →