Import a role from a URL (GitHub, raw URL, etc.)
AI agents use roles_import 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.
This tool fetches content from an external URL and writes it into the local role library. It creates new data (a role entry) in the local storage, which is a Write operation. The severity is medium because it pulls external content that could introduce malicious prompts or personas, but the operation is reversible (the role can be removed with roles_remove).
From the tool's definition Import a role from a URL (GitHub, raw URL, etc.)
Attacks that exploit this kind of access
Import a role from a URL (GitHub, raw URL, etc.). 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.
Register the Claude Role Library MCP server in PolicyLayer and add a rule for roles_import: 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.
roles_import 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 roles_import 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 roles_import. 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.
roles_import 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →