update_memory_from_input · Apple Calendar MCP: Risk & Policy

WHAT IT DOES

What update_memory_from_input does on Apple Calendar MCP

AI agents use update_memory_from_input to create or update resources in Apple Calendar MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Calendar MCP environment.

WHY IT NEEDS A POLICY

Why update_memory_from_input needs a policy

An AI agent can call update_memory_from_input faster than any human can review — one bad instruction and it creates or modifies resources in Apple Calendar MCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_memory_from_input Rate-limited

update_memory_from_input 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": {
    "update_memory_from_input": {
      "limits": [
        {
          "counter": "update_memory_from_input_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 Apple Calendar MCP, so you can run agents against it safely.

FAQ

Questions about update_memory_from_input

What does the update_memory_from_input tool do? +

Stage 3. Bulk-merges extraction results + research into memory. It is categorised as a Write tool in the Apple Calendar MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_memory_from_input? +

Register the Apple Calendar MCP server in PolicyLayer and add a rule for update_memory_from_input: 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 Apple Calendar MCP. Nothing to install.

What risk level is update_memory_from_input? +

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

Can I rate-limit update_memory_from_input? +

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

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

update_memory_from_input is provided by the Apple Calendar MCP server (yongzhe-wang/yapping-apple-calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.