Compose a scheduling proposal message with proposed time slots. Formats times in the specified timezone for email, Slack, or SMS. Does NOT send the message — returns formatted text for the agent to send via its channel MCP (Gmail, Slack, etc.).
AI agents use compose_proposal to create or update resources in Temporal Cortex Calendar MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Temporal Cortex Calendar MCP environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
format | string | null | — | Output format: "email" (default), "slack", or "sms". |
timezone | string | Yes | Display timezone for the message (IANA, e.g., "America/New_York"). |
contact_name | string | Yes | Name of the person to schedule with. |
contact_email | string | Yes | Email address of the contact. |
meeting_title | string | null | — | Optional meeting title. |
proposed_slots | array | Yes | Proposed time slots (from find_free_slots). |
duration_minutes | integer | Yes | Meeting duration in minutes. |
temporal_link_slug | string | null | — | Temporal Link slug if the recipient has Open Scheduling. |
meeting_description | string | null | — | Optional meeting description. |
Parameters from the server's own tool schema.
An AI agent can call compose_proposal faster than any human can review — one bad instruction and it creates or modifies resources in Temporal Cortex Calendar MCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Compose a scheduling proposal message with proposed time slots. Formats times in the specified timezone for email, Slack, or SMS. Does NOT send the message — returns formatted text for the agent to send via its channel MCP (Gmail, Slack, etc.). It is categorised as a Write tool in the Temporal Cortex Calendar MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
compose_proposal accepts 9 parameters: format, timezone, contact_name, contact_email, meeting_title, proposed_slots, duration_minutes, temporal_link_slug, meeting_description. Required: timezone, contact_name, contact_email, proposed_slots, duration_minutes. The full parameter table on this page comes from the server's own tool schema.
Register the Temporal Cortex Calendar MCP server in PolicyLayer and add a rule for compose_proposal: 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 Temporal Cortex Calendar MCP. Nothing to install.
compose_proposal 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 compose_proposal 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 compose_proposal. 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.
compose_proposal is provided by the Temporal Cortex Calendar MCP server (temporal-cortex/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.