Assign the agent that handles inbound conversations on a given channel. When a message arrives on the channel (email, Slack DM, WhatsApp message, Signal message), it is routed to this agent's chat endpoint. The agent's instructions and tools are used to compose a reply, which is sent back through...
Part of the Agentled server.
Free to start. No card required.
AI agents use set_channel_default_agent to create or modify resources in Agentled. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call set_channel_default_agent repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Agentled.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"set_channel_default_agent": {
"limits": [
{
"counter": "set_channel_default_agent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Agentled policy for all 119 tools.
These attack patterns abuse exactly the kind of access set_channel_default_agent gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Assign the agent that handles inbound conversations on a given channel. When a message arrives on the channel (email, Slack DM, WhatsApp message, Signal message), it is routed to this agent's chat endpoint. The agent's instructions and tools are used to compose a reply, which is sent back through the originating channel. Use list_channels to inspect current assignments and list_agents to find valid agent IDs. Use configure_channel for more granular updates (enable/disable, allowedSenders, etc.).. It is categorised as a Write tool in the Agentled MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agentled MCP server in PolicyLayer and add a rule for set_channel_default_agent: 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 Agentled. Nothing to install.
set_channel_default_agent 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 set_channel_default_agent 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 set_channel_default_agent. 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.
set_channel_default_agent is provided by the Agentled MCP server (@agentled/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 119 Agentled tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.