fruityvice_by_name
Get detailed nutrition info for a specific fruit from Fruityvice.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/fruityvice-by-name.md
What fruityvice_by_name does on UnClick
AI agents call fruityvice_by_name to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Fruit name (e.g. banana, apple, strawberry). |
Parameters from the server's own tool schema.
Why fruityvice_by_name is rated Low
This tool queries a nutrition database (Fruityvice) and returns read-only information about fruits. It has no capability to modify, delete, or execute arbitrary operations. The blast radius of misuse is minimal—an agent could retrieve excessive nutrition data but cannot harm systems or data integrity. Classified as Read with low severity.
From the tool's definition Tool description states 'Get detailed nutrition info for a specific fruit' — a retrieval operation with no modifications, deletions, or side effects.
Attacks that exploit this kind of access
The rule that runs fruityvice_by_name safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fruityvice_by_name, this is the rule to start with:
fruityvice_by_name is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every fruityvice_by_name call is checked against it from then on.
Questions about fruityvice_by_name
Get detailed nutrition info for a specific fruit from Fruityvice. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
fruityvice_by_name accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for fruityvice_by_name: 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 UnClick. Nothing to install.
fruityvice_by_name 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 fruityvice_by_name 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 fruityvice_by_name. 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.
fruityvice_by_name is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue