Get time slots (internal calendar blocks that don
AI agents call get-time-slots 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 calendar time slot data. It is a read-only query operation that retrieves or lists data without creating, modifying, deleting, or executing operations. No destructive, financial, or execution capabilities are indicated. The incomplete description lowers confidence slightly from maximum, but the Get/retrieval semantics are unambiguous.
From the tool's definition Tool name 'get-time-slots' and description prefix 'Get time slots' indicate a retrieval operation. The description is incomplete ('that don') but the verb 'Get' clearly signals a read-only query action without modification or side effects.
Documented attack patterns abuse exactly the kind of access get-time-slots 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-time-slots:
{
"version": "1",
"default": "deny",
"tools": {
"get-time-slots": {}
}
} get-time-slots 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 time slots (internal calendar blocks that don. 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-time-slots: 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-time-slots 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-time-slots 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-time-slots. 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-time-slots 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.