sources_import_all · Claude Role Library MCP: Risk & Policy

WHAT IT DOES

What sources_import_all does on Claude Role Library

AI agents use sources_import_all 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 sources_import_all needs a policy

This tool writes data to the system by importing role definitions from an external GitHub source into the local storage. While the import itself is reversible (roles can be removed via roles_clear or other deletion operations), it modifies the system state. It does not execute arbitrary code or delete data irreversibly, nor does it involve financial transactions.

From the tool's definition Tool is named 'sources_import_all' and description states it 'Import[s] all roles from a source (GitHub repository)'. The action creates or modifies data (importing roles into the local YAML-based storage system) in a reversible manner.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sources_import_all Rate-limited

sources_import_all 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": {
    "sources_import_all": {
      "limits": [
        {
          "counter": "sources_import_all_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 sources_import_all

What does the sources_import_all tool do? +

Import all roles from a source (GitHub repository). 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 sources_import_all? +

Register the Claude Role Library MCP server in PolicyLayer and add a rule for sources_import_all: 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 sources_import_all? +

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

Can I rate-limit sources_import_all? +

Yes. Add a rate_limit block to the sources_import_all 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 sources_import_all completely? +

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

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