Answer a natural-language hair question (frizz, breakage, color care, blonde maintenance, smoothing, hair loss, curls, scalp, etc.) with a short expert tip and 1-3 Prohall product recommendations (with URLs to prohall.net). This is the primary tool to call when a user asks for hair advice. Suppor...
Part of the Hair server.
Free to start. No card required.
AI agents call answer_hair_question to retrieve information from Hair without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though answer_hair_question only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"answer_hair_question": {}
}
}See the full Hair policy for all 6 tools.
These attack patterns abuse exactly the kind of access answer_hair_question gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Answer a natural-language hair question (frizz, breakage, color care, blonde maintenance, smoothing, hair loss, curls, scalp, etc.) with a short expert tip and 1-3 Prohall product recommendations (with URLs to prohall.net). This is the primary tool to call when a user asks for hair advice. Supports 6 languages: en, es, fr, de, ja, pt.. It is categorised as a Read tool in the Hair MCP Server, which means it retrieves data without modifying state.
Register the Hair MCP server in PolicyLayer and add a rule for answer_hair_question: 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 Hair. Nothing to install.
answer_hair_question 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 answer_hair_question 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 answer_hair_question. 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.
answer_hair_question is provided by the Hair MCP server (prohall/hair). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Hair tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.