Invite a family member to your cookbook. They can view recipes (viewer) or view and add (editor).
AI agents use family_invite to create or update resources in Old Family Recipe — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Old Family Recipe environment.
This tool creates new access records (invitations/memberships) in the cookbook system, which is a reversible write operation. While it modifies permissions rather than recipe data directly, it materially changes the state of the application by granting users access rights and roles.
From the tool's definition Tool description states 'Invite a family member to your cookbook' and grants permission levels ('viewer' or 'editor'), indicating it creates or modifies access control records and cookbook membership.
Attacks that exploit this kind of access
Invite a family member to your cookbook. They can view recipes (viewer) or view and add (editor). It is categorised as a Write tool in the Old Family Recipe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Old Family Recipe MCP server in PolicyLayer and add a rule for family_invite: 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 Old Family Recipe. Nothing to install.
family_invite 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 family_invite 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 family_invite. 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.
family_invite is provided by the Old Family Recipe MCP server (oldfamilyrecipe/ai). 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 →