yaag_create_event · YearAtAGlance MCP Server MCP

WHAT IT DOES

What yaag_create_event does on YearAtAGlance MCP Server

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

WHY IT NEEDS A POLICY

Why yaag_create_event needs a policy

Creating calendar events is a Write operation: it adds new data to the system reversibly without executing arbitrary code, triggering external operations, deleting data, or moving money. The severity is low because calendar event creation has minimal blast radius—unwanted events can be easily removed, and calendar data is typically non-critical.

From the tool's definition Tool name 'yaag_create_event' and description 'Create a new event in the YearAtAGlance calendar' explicitly indicate data creation. This is a reversible operation—events can be modified or deleted later, as evidenced by the sibling tool 'yaag_delete_event'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

yaag_create_event Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "yaag_create_event": {
      "limits": [
        {
          "counter": "yaag_create_event_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 YearAtAGlance MCP Server, so you can run agents against it safely.

FAQ

Questions about yaag_create_event

What does the yaag_create_event tool do? +

Create a new event in the YearAtAGlance calendar. Dates should be in ISO 8601 format. It is categorised as a Write tool in the YearAtAGlance 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 yaag_create_event? +

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

What risk level is yaag_create_event? +

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

Can I rate-limit yaag_create_event? +

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

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

yaag_create_event is provided by the YearAtAGlance MCP Server MCP server (mindfullabai/yearataglance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.