yaag_update_category · YearAtAGlance MCP Server MCP

WHAT IT DOES

What yaag_update_category does on YearAtAGlance MCP Server

AI agents use yaag_update_category 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_update_category needs a policy

This tool modifies existing calendar category data, which classifies it as Write rather than Read (retrieval only) or Destructive (irreversible deletion). The severity is medium because misuse could corrupt calendar organization or metadata, but the impact is localized to category properties and reversible.

From the tool's definition Tool name 'yaag_update_category' and description 'Update an existing category' indicate modification of calendar category data. The 'update' operation is reversible (can be changed again) and affects metadata rather than core data deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

yaag_update_category Rate-limited

yaag_update_category 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_update_category": {
      "limits": [
        {
          "counter": "yaag_update_category_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_update_category

What does the yaag_update_category tool do? +

Update an existing category. 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_update_category? +

Register the YearAtAGlance MCP Server MCP server in PolicyLayer and add a rule for yaag_update_category: 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_update_category? +

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

Can I rate-limit yaag_update_category? +

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

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

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