resolve_identity · Temporal Cortex Calendar MCP

WHAT IT DOES

What resolve_identity does on Temporal Cortex Calendar MCP

AI agents use resolve_identity 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.

PARAMETERS

Parameter	Type	Required	Description
`identity`	string	Yes	Email address, phone number, or agent ID to resolve to a Temporal Link slug.

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why resolve_identity needs a policy

An AI agent can call resolve_identity 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

Recommended rule Ready

Verdict

resolve_identity Rate-limited

resolve_identity 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": {
    "resolve_identity": {
      "limits": [
        {
          "counter": "resolve_identity_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Temporal Cortex Calendar MCP, so you can run agents against it safely.

FAQ

Questions about resolve_identity

What does the resolve_identity tool do? +

Resolve an email, phone, or agent ID to a Temporal Cortex slug (DNS for Human Time). Use this to find someone's Open Scheduling profile before querying their availability or booking a meeting. Requires Platform Mode. 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.

What parameters does resolve_identity accept? +

resolve_identity accepts 1 parameter: identity. Required: identity. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on resolve_identity? +

Register the Temporal Cortex Calendar MCP server in PolicyLayer and add a rule for resolve_identity: 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.

What risk level is resolve_identity? +

resolve_identity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit resolve_identity? +

Yes. Add a rate_limit block to the resolve_identity 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 resolve_identity completely? +

Set action: deny in the PolicyLayer policy for resolve_identity. 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 resolve_identity? +

resolve_identity 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.