Update household family profile (members, ages, preferences)
AI agents use update_family_profile to create or update resources in Mcp Veggie — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Veggie environment.
This tool creates or modifies user profile data without deleting or destroying it, making it a Write operation. Severity is medium because misuse could expose or alter personal information about household members (names, ages, dietary preferences), which has privacy implications but is reversible and localized to user-owned data with no financial, destructive, or code execution risks.
From the tool's definition Tool updates household family profile data (members, ages, preferences) — a reversible modification operation that changes stored user information.
Attacks that exploit this kind of access
Update household family profile (members, ages, preferences). It is categorised as a Write tool in the Mcp Veggie MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Veggie MCP server in PolicyLayer and add a rule for update_family_profile: 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 Mcp Veggie. Nothing to install.
update_family_profile 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 update_family_profile 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 update_family_profile. 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.
update_family_profile is provided by the Mcp Veggie MCP server (lovettbarron/mcp-veggiebox). 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 →