Assign a task to an AI agent
AI agents invoke assign_task to trigger actions in Shannon MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Assigning a task to an AI agent initiates autonomous execution of potentially arbitrary operations. The actual impact depends on what the agent does, but since this is part of a multi-agent collaborative system managing Claude Code CLI operations, the assigned tasks could include code execution, file modifications, or other high-impact actions.
From the tool's definition 'Assign a task to an AI agent' — triggers external AI agent operations whose effects depend on the task arguments
Attacks that exploit this kind of access
Assign a task to an AI agent. It is categorised as a Execute tool in the Shannon MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Shannon MCP server in PolicyLayer and add a rule for assign_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 Shannon MCP. Nothing to install.
assign_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the assign_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 assign_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.
assign_task is provided by the Shannon MCP server (krzemienski/shannon-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 →