Get a specific perfume by its ID
AI agents call get_perfume_by_id 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 a single perfume record by ID. It performs a read-only query operation with no capability to modify, delete, or execute external actions. The sibling tools (list_all_perfumes, search_perfumes) are also read operations, and only get_purchase_link and implied purchase functionality would involve financial transactions.
From the tool's definition Tool name is 'get_perfume_by_id' and description states 'Get a specific perfume by its ID' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get a specific perfume by its ID. 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 get_perfume_by_id: 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.
get_perfume_by_id 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 get_perfume_by_id 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 get_perfume_by_id. 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.
get_perfume_by_id 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 →