Install a SkillMesh role bundle by id or friendly name.
AI agents use install_skillmesh_role to create or update resources in SkillMesh — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SkillMesh environment.
Installing a role bundle modifies the system configuration by adding new capabilities or permissions, making this a Write operation (reversible state change). Severity is medium because installing arbitrary role bundles could expand attack surface or grant unintended permissions, but the impact depends on what the bundle contains and the permissions model.
From the tool's definition Tool description states 'Install a SkillMesh role bundle by id or friendly name.' The verb 'install' indicates modification of system state by adding/activating a new role bundle.
Documented attack patterns abuse exactly the kind of access install_skillmesh_role gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SkillMesh, and nothing reaches the server without passing your rules. This is the rule we recommend for install_skillmesh_role:
{
"version": "1",
"default": "deny",
"tools": {
"install_skillmesh_role": {
"limits": [
{
"counter": "install_skillmesh_role_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}install_skillmesh_role stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Install a SkillMesh role bundle by id or friendly name. It is categorised as a Write tool in the SkillMesh MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SkillMesh MCP server in PolicyLayer and add a rule for install_skillmesh_role: 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 SkillMesh. Nothing to install.
install_skillmesh_role 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 install_skillmesh_role 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 install_skillmesh_role. 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.
install_skillmesh_role is provided by the SkillMesh MCP server (varunreddy/skillmesh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SkillMesh, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 SkillMesh tools catalogued and risk-classified — across an index of 43,000+ MCP servers.