Low Risk

search_events

Search for calendar events

How to control search_events ↓

What search_events does on Python Apple MCP

AI agents call search_events to retrieve information from Python Apple MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_events needs a policy

Calendar event searches retrieve information without side effects. The worst case misuse would expose calendar data the AI shouldn't see, but this is a relatively low-blast-radius information disclosure. No creation, modification, deletion, code execution, or financial impact is possible with this tool.

From the tool's definition Tool description explicitly states 'Search for calendar events' - a query/retrieval operation with no data modification capability.

Documented attack patterns abuse exactly the kind of access search_events gives an agent:

How to control search_events

PolicyLayer is an MCP gateway — it sits between your AI agents and Python Apple MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_events:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_events": {}
  }
}

search_events is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Python Apple MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_events

What does the search_events tool do? +

Search for calendar events. It is categorised as a Read tool in the Python Apple MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_events? +

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

What risk level is search_events? +

search_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_events? +

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

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

search_events is provided by the Python Apple MCP server (jxnl/python-apple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Python Apple MCP tool call.

Start from Python Apple MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

13 Python Apple MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.