List all perfumes in the Blue Perfumery collection
AI agents call list_all_perfumes to retrieve information from Blue Perfumery MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents existing data from a perfume catalog without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk—users can only view publicly available product information. The blast radius of misuse is negligible, as listing products cannot harm systems or data integrity.
From the tool's definition Tool name 'list_all_perfumes' and description 'List all perfumes in the Blue Perfumery collection' indicate a retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
List all perfumes in the Blue Perfumery collection. It is categorised as a Read tool in the Blue Perfumery MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Blue Perfumery MCP Server MCP server in PolicyLayer and add a rule for list_all_perfumes: 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 Blue Perfumery MCP Server. Nothing to install.
list_all_perfumes 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_all_perfumes 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_all_perfumes. 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_all_perfumes is provided by the Blue Perfumery MCP Server MCP server (recepgocmen/blue-perfumery-mcp-server). 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 →