Resolve a contact's email to available scheduling paths. Returns the best way to schedule with them: Open Scheduling (instant booking), email, or phone. Call after search_contacts to determine the scheduling method.
AI agents use resolve_contact 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 |
|---|---|---|---|
email | string | Yes | Email address of the contact to resolve scheduling paths for. |
phone | string | null | — | Optional phone number (used as a fallback scheduling channel). |
Parameters from the server's own tool schema.
An AI agent can call resolve_contact 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
Resolve a contact's email to available scheduling paths. Returns the best way to schedule with them: Open Scheduling (instant booking), email, or phone. Call after search_contacts to determine the scheduling method. 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.
resolve_contact accepts 2 parameters: email, phone. Required: email. 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 resolve_contact: 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.
resolve_contact 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 resolve_contact 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 resolve_contact. 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.
resolve_contact 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.