Medium Risk

edit-event

Edit a calendar event. Changes sync back to the source calendar (Google, etc.)

How to control edit-event ↓

What edit-event does on Akiflow MCP Server

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

Medium Risk

Why edit-event needs a policy

This tool creates or modifies data reversibly by editing calendar events. While the changes persist externally, they are not destructive (the event is not deleted) and do not involve financial transactions or code execution.

From the tool's definition Tool description states 'Edit a calendar event. Changes sync back to the source calendar' — modifies calendar data reversibly with side effects that propagate to external systems (Google Calendar, etc.).

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

How to control edit-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 edit-event:

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

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

  1. Create a free account and register Akiflow MCP Server — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about edit-event

What does the edit-event tool do? +

Edit a calendar event. Changes sync back 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 edit-event? +

Register the Akiflow MCP Server MCP server in PolicyLayer and add a rule for edit-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 edit-event? +

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

Can I rate-limit edit-event? +

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

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

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

Free to start. No card required.

22 Akiflow MCP Server 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.