Assign one or more users to a task. POST to /tasks/{id}/assign.
AI agents use task.assign to create or update resources in Freedcamp MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freedcamp MCP Server environment.
This tool creates or modifies task assignments, which is a reversible change to task state. It does not execute arbitrary code, delete data irreversibly, or move money. The POST operation and ability to reassign users confirm it is Write-category. Severity is medium because incorrect assignments could disrupt team workflows, but the change is easily reversible through reassignment.
From the tool's definition Tool description states 'Assign one or more users to a task' with POST request to /tasks/{id}/assign. Assignment modifies task metadata (user associations) reversibly without deleting or destroying data.
Attacks that exploit this kind of access
Assign one or more users to a task. POST to /tasks/{id}/assign. It is categorised as a Write tool in the Freedcamp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freedcamp MCP Server MCP server in PolicyLayer and add a rule for task.assign: 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 Freedcamp MCP Server. Nothing to install.
task.assign 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 task.assign 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 task.assign. 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.
task.assign is provided by the Freedcamp MCP Server MCP server (mahrukh-n8n/freedcampmcp). 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 →