remove_workers
AI agents use remove_workers to create or update resources in Freelo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freelo MCP Server environment.
Based on the tool name alone, 'remove_workers' likely unassigns or removes workers/members from tasks or projects in Freelo. This is a reversible write operation (workers can be re-added), placing it in the Write category. However, confidence is low due to the empty description. Severity is medium because misuse could disrupt team assignments and project workflows.
From the tool's definition Tool name 'remove_workers' suggests removing worker assignments from tasks or projects; description is empty and uninformative.
Attacks that exploit this kind of access
remove_workers. It is categorised as a Write tool in the Freelo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freelo MCP Server MCP server in PolicyLayer and add a rule for remove_workers: 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 Freelo MCP Server. Nothing to install.
remove_workers 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 remove_workers 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 remove_workers. 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.
remove_workers is provided by the Freelo MCP Server MCP server (m-hlpr/freelo-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 →