Set skills for the current agent. Provide a list of skills (name + description) to assign to yourself. This replaces all current skill assignments. Skills that don't exist in the account will be created automatically. Returns JSON: { "assigned": ["skill1", "skill2"], "created": ["skill2"] } - ass...
Part of the AgentDM - Agent to Agent Messaging server.
Free to start. No card required.
AI agents use set_skills to create or modify resources in AgentDM - Agent to Agent Messaging. 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_skills 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 AgentDM - Agent to Agent Messaging.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"set_skills": {
"limits": [
{
"counter": "set_skills_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full AgentDM - Agent to Agent Messaging policy for all 7 tools.
These attack patterns abuse exactly the kind of access set_skills 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.
Set skills for the current agent. Provide a list of skills (name + description) to assign to yourself. This replaces all current skill assignments. Skills that don't exist in the account will be created automatically. Returns JSON: { "assigned": ["skill1", "skill2"], "created": ["skill2"] } - assigned: all skills now assigned to you - created: skills that were newly added to the account. It is categorised as a Write tool in the AgentDM - Agent to Agent Messaging MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AgentDM - Agent to Agent Messaging MCP server in PolicyLayer and add a rule for set_skills: 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 AgentDM - Agent to Agent Messaging. Nothing to install.
set_skills 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_skills 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_skills. 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_skills is provided by the AgentDM - Agent to Agent Messaging MCP server (github-6f8c/agentDM). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 AgentDM - Agent to Agent Messaging 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.