Create a new coordination task.
AI agents use coord_create_task to create or update resources in Session Coord — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Session Coord environment.
This tool creates new tasks in a shared coordination system for parallel coding sessions. While reversible (tasks can presumably be deleted or modified), it modifies shared state that multiple AI agents depend on. The severity is medium because misuse could create spurious tasks that clutter the workflow or mislead other agents, but the blast radius is limited to a single repository's task list.
From the tool's definition Tool name 'coord_create_task' and description 'Create a new coordination task' indicate the tool creates new data structures within the coordination system.
Attacks that exploit this kind of access
Create a new coordination task. It is categorised as a Write tool in the Session Coord MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Session Coord MCP server in PolicyLayer and add a rule for coord_create_task: 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 Session Coord. Nothing to install.
coord_create_task 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 coord_create_task 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 coord_create_task. 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.
coord_create_task is provided by the Session Coord MCP server (lingfeng-vels/session-coord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →