Assign a confirmed finding to a developer agent to fix, creating a linked
AI agents use assign_fix to create or update resources in Claude Team MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Team MCP environment.
This tool creates or modifies work assignments within a team coordination system. It generates new task records linking findings to developers, which is a reversible write operation. It does not execute code, delete data irreversibly, move funds, or trigger external systems directly—it simply organizes work items within the MCP server's internal state.
From the tool's definition Tool name 'assign_fix' and description 'Assign a confirmed finding to a developer agent to fix, creating a linked' indicates creation/modification of task assignments and work items.
Attacks that exploit this kind of access
Assign a confirmed finding to a developer agent to fix, creating a linked. It is categorised as a Write tool in the Claude Team MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Team MCP server in PolicyLayer and add a rule for assign_fix: 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 Claude Team MCP. Nothing to install.
assign_fix 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 assign_fix 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 assign_fix. 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.
assign_fix is provided by the Claude Team MCP server (lakshan12367/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 →