AI agents call skin_list to retrieve information from Cartridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of existing personality skins without modifying, deleting, or executing any operations. It is a straightforward read operation similar to list or get operations, posing minimal security risk.
From the tool's definition Tool name 'skin_list' and description 'List all available personality skins' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all available personality skins. It is categorised as a Read tool in the Cartridge MCP Server, which means it retrieves data without modifying state.
Register the Cartridge MCP server in PolicyLayer and add a rule for skin_list: 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 Cartridge. Nothing to install.
skin_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the skin_list 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 skin_list. 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.
skin_list is provided by the Cartridge MCP server (lucineer/cartridge-mcp). 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 →