convert_time · Calendar App MCP: Risk & Policy

WHAT IT DOES

What convert_time does on Calendar App

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

WHY IT NEEDS A POLICY

Why convert_time needs a policy

An AI agent can call convert_time faster than any human can review — one bad instruction and it creates or modifies resources in Calendar App by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

convert_time Rate-limited

convert_time 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": {
    "convert_time": {
      "limits": [
        {
          "counter": "convert_time_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 Calendar App, so you can run agents against it safely.

FAQ

Questions about convert_time

What does the convert_time tool do? +

convert_time. It is categorised as a Write tool in the Calendar App MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on convert_time? +

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

What risk level is convert_time? +

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

Can I rate-limit convert_time? +

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

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

convert_time is provided by the Calendar App MCP server (rygwdn/calendar-app-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.