AI agents call list_style_fingerprints to retrieve information from Orpheus 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 pre-computed style fingerprint data. It has no side effects, does not modify any state, and does not execute commands or delete data. It is a straightforward data retrieval operation, making it a Read category tool with low severity.
From the tool's definition Tool name uses 'list' and description states 'List cached target fingerprints' — a retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
List cached target fingerprints (e.g. 'classical', 'hiphop', 'dominic-fike-sunburn'). It is categorised as a Read tool in the Orpheus MCP Server, which means it retrieves data without modifying state.
Register the Orpheus MCP server in PolicyLayer and add a rule for list_style_fingerprints: 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 Orpheus. Nothing to install.
list_style_fingerprints 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 list_style_fingerprints 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 list_style_fingerprints. 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.
list_style_fingerprints is provided by the Orpheus MCP server (mal0ware/orpheus). 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 →