roles_add · Claude Role Library MCP: Risk & Policy

WHAT IT DOES

What roles_add does on Claude Role Library

AI agents use roles_add to create or update resources in Claude Role Library — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Role Library environment.

WHY IT NEEDS A POLICY

Why roles_add needs a policy

This tool creates new role definitions (personas/prompts) in a local YAML-based storage system. While reversible via roles_remove, it modifies the stored configuration state. No irreversible deletion, code execution, or financial impact occurs. The impact is scoped to role management, making it Write rather than Execute or Destructive.

From the tool's definition Tool description states 'Add a new role', which creates a new data record in the roles system. The sibling tools (roles_list, roles_get, roles_remove, roles_import, roles_clear) and the YAML-based storage context confirm this is a data creation operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

roles_add Rate-limited

roles_add 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "roles_add": {
      "limits": [
        {
          "counter": "roles_add_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude Role Library, so you can run agents against it safely.

FAQ

Questions about roles_add

What does the roles_add tool do? +

Add a new role. It is categorised as a Write tool in the Claude Role Library MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on roles_add? +

Register the Claude Role Library MCP server in PolicyLayer and add a rule for roles_add: 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 Role Library. Nothing to install.

What risk level is roles_add? +

roles_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit roles_add? +

Yes. Add a rate_limit block to the roles_add 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.

How do I block roles_add completely? +

Set action: deny in the PolicyLayer policy for roles_add. 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.

What MCP server provides roles_add? +

roles_add is provided by the Claude Role Library MCP server (tony427/claude-role-library). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.