Helps the user create a recipe based on their needs.
AI agents use elicit_user_needs to create or update resources in Recettes MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Recettes MCP Server environment.
The tool description is vague but implies guiding a user through creating a recipe, which is a Write-level operation (creating data). However, the description is uninformative about exact mechanics — it could be merely a Read/query operation that elicits preferences before passing to another tool. Confidence is lowered due to the ambiguous description.
From the tool's definition 'Helps the user create a recipe based on their needs'
Attacks that exploit this kind of access
Helps the user create a recipe based on their needs. It is categorised as a Write tool in the Recettes MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Recettes MCP Server MCP server in PolicyLayer and add a rule for elicit_user_needs: 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 Recettes MCP Server. Nothing to install.
elicit_user_needs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the elicit_user_needs 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 elicit_user_needs. 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.
elicit_user_needs is provided by the Recettes MCP Server MCP server (symfomany/mcp-tuto). 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 →