AI agents use menami_manage_occasions to create or update resources in Menami — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Menami environment.
This tool creates or modifies occasion data (birthdays, anniversaries, trips) in the user's profile. It is reversible (occasions can be edited, deleted, or updated), causes no financial transactions or irreversible deletions, and does not execute arbitrary code. It fits the Write category: creates or modifies data reversibly.
From the tool's definition Tool name 'menami_manage_occasions' and description 'Set up special occasions' indicate creating or modifying occasion records. Verb 'Set up' signals data creation/modification.
Attacks that exploit this kind of access
Set up special occasions (birthdays, anniversaries, trips) and get. It is categorised as a Write tool in the Menami MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Menami MCP server in PolicyLayer and add a rule for menami_manage_occasions: 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 Menami. Nothing to install.
menami_manage_occasions 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 menami_manage_occasions 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 menami_manage_occasions. 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.
menami_manage_occasions is provided by the Menami MCP server (menami-ai/menami). 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 →