Get all calendars. Returns calendar metadata including colors, settings, and sync status.
AI agents call get-calendars to retrieve information from Akiflow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries calendar metadata without side effects. It fetches existing data (colors, settings, sync status) but does not create, modify, delete, or execute operations. This is a straightforward Read operation with minimal risk—calendar metadata is typically non-sensitive configuration data. Even if an agent calls this repeatedly, no harm occurs.
From the tool's definition Tool name 'get-calendars' and description 'Get all calendars. Returns calendar metadata including colors, settings, and sync status.' indicate pure data retrieval with no modification, creation, or deletion of resources.
Documented attack patterns abuse exactly the kind of access get-calendars gives an agent:
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 get-calendars:
{
"version": "1",
"default": "deny",
"tools": {
"get-calendars": {}
}
} get-calendars is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all calendars. Returns calendar metadata including colors, settings, and sync status. It is categorised as a Read tool in the Akiflow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Akiflow MCP Server MCP server in PolicyLayer and add a rule for get-calendars: 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.
get-calendars is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-calendars 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.
Set action: deny in the PolicyLayer policy for get-calendars. 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.
get-calendars 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.
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.