Add a task to a time slot. Links the task to an existing time slot block on the calendar.
AI agents use add-task-to-timeslot to create or update resources in Akiflow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Akiflow MCP Server environment.
This tool creates or modifies task-calendar associations reversibly. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). The action is a standard write operation that modifies the task management state.
From the tool's definition Tool description states 'Add a task to a time slot' and 'Links the task to an existing time slot block on the calendar.' The verb 'Add' and the action of linking/associating a task with a calendar time slot indicates creation or modification of a relationship…
Documented attack patterns abuse exactly the kind of access add-task-to-timeslot 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 add-task-to-timeslot:
{
"version": "1",
"default": "deny",
"tools": {
"add-task-to-timeslot": {
"limits": [
{
"counter": "add-task-to-timeslot_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add-task-to-timeslot 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.
Free to start. No card required.
Add a task to a time slot. Links the task to an existing time slot block on the calendar. It is categorised as a Write tool in the Akiflow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Akiflow MCP Server MCP server in PolicyLayer and add a rule for add-task-to-timeslot: 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.
add-task-to-timeslot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add-task-to-timeslot 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 add-task-to-timeslot. 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.
add-task-to-timeslot 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.