add-event

THE RISK

Medium Risk

Why add-event needs a policy

This tool creates a new calendar event and persists it to an external calendar service (Google Calendar or similar). This is a Write operation—it modifies state irreversibly in the sense that the event now exists in the user's calendar and may affect schedules, notifications, and third-party integrations.

From the tool's definition Tool name 'add-event' and description 'Create a new calendar event. Syncs to the source calendar (Google, etc.)' indicate creation of new data.

Documented attack patterns abuse exactly the kind of access add-event gives an agent:

POLICY

How to control add-event

PolicyLayer is an MCP gateway — it sits between your AI agents and Akiflow MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add-event:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add-event": {
      "limits": [
        {
          "counter": "add-event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

add-event 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.

Create a free account and register Akiflow MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Akiflow MCP Server tools

Write remove-task-from-timeslot Remove a task from its time slot. Unlinks the task from its associated time slot block. Write unschedule-task Remove a task from the calendar and optionally move to inbox Write add-task Create a new task in Akiflow Write add-task-to-timeslot Add a task to a time slot. Links the task to an existing time slot block on the calendar. Write add-time-slot Create a time slot (internal calendar block). Does not sync to external calendars. Write create-task-from-action-item Create an Akiflow task from a meeting recording Write edit-event Edit a calendar event. Changes sync back to the source calendar (Google, etc.) Write edit-task Update an existing task

All 22 Akiflow MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about add-event

What does the add-event tool do? +

Create a new calendar event. Syncs to the source calendar (Google, etc.). It is categorised as a Write tool in the Akiflow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add-event? +

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

What risk level is add-event? +

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

Can I rate-limit add-event? +

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

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

add-event is provided by the Akiflow MCP Server MCP server (shrimpwtf/akiflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Akiflow MCP Server tool call.

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

CHECK YOUR STACK →