batch_assign_timeframes
A write tool on the Coach AI MCP server.
This record as markdown: /tools/94aharris-coach-ai/batch-assign-timeframes.md
What batch_assign_timeframes does on Coach AI
AI agents use batch_assign_timeframes to create or update resources in Coach AI, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coach AI environment.
Why batch_assign_timeframes is rated Medium
The tool appears to update task timeframes in bulk, which is a write operation that modifies task metadata. While the description is empty, the naming pattern and context from sibling tools strongly indicate data modification. This is classified as Write rather than Execute because it appears to update existing task properties rather than trigger external actions or code execution.
From the tool's definition Tool name 'batch_assign_timeframes' suggests bulk modification of task scheduling/timing data. Sibling tools like 'add_todo', 'complete_todo', and 'break_down_task' indicate this server manages task state.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_assign_timeframes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Coach AI, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For batch_assign_timeframes, this is the rule to start with:
batch_assign_timeframes 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Coach AI, apply this rule, and every batch_assign_timeframes call is checked against it from then on.
Questions about batch_assign_timeframes
batch_assign_timeframes is a write tool on the Coach AI MCP server. It is categorised as a Write tool in the Coach AI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coach AI MCP server in PolicyLayer and add a rule for batch_assign_timeframes: 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 Coach AI. Nothing to install.
batch_assign_timeframes 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 batch_assign_timeframes 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 batch_assign_timeframes. 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.
batch_assign_timeframes is provided by the Coach AI MCP server (94aharris/coach-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Coach AI, and thousands of servers like it.
This server
Across the catalogue