AI agents call human_nose_tool to retrieve information from Human without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool requests human sensory perception (smell detection) and returns the result to the AI assistant. It is purely informational with no side effects, data modification, code execution, or irreversible actions. It fits the Read category as a sensory query operation analogous to human_eye_tool (visual information retrieval) or human_ear_tool (auditory information retrieval).
From the tool's definition Tool description states it allows humans to use their nose to confirm/check smells (人間が鼻を使って匂いを確認します). This is a sensory input operation that retrieves olfactory information without modifying, executing external operations, or causing destructive effects.
Documented attack patterns abuse exactly the kind of access human_nose_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Human, and nothing reaches the server without passing your rules. This is the rule we recommend for human_nose_tool:
{
"version": "1",
"default": "deny",
"tools": {
"human_nose_tool": {}
}
}human_nose_tool is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
人間が鼻を使って匂いを確認します。. It is categorised as a Read tool in the Human MCP Server, which means it retrieves data without modifying state.
Register the Human MCP server in PolicyLayer and add a rule for human_nose_tool: 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 Human. Nothing to install.
human_nose_tool 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 human_nose_tool 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 human_nose_tool. 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.
human_nose_tool is provided by the Human MCP server (upamune/human-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Human tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Human tools catalogued and risk-classified — across an index of 42,500+ MCP servers.