AI agents use memento_configure_notifications to create or update resources in Memento — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memento environment.
This tool creates or modifies notification configuration settings (enable/disable toggles, topic selections, threshold parameters). These are reversible changes to system state without side effects beyond the notification system itself. It does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial).
From the tool's definition Tool description states 'Configure notification settings — enable/disable, set topics, set confidence threshold.' The configure/set actions modify system settings reversibly.
Attacks that exploit this kind of access
[DEPRECATED] Configure notification settings — enable/disable, set topics, set confidence threshold. It is categorised as a Write tool in the Memento MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memento MCP server in PolicyLayer and add a rule for memento_configure_notifications: 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 Memento. Nothing to install.
memento_configure_notifications 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 memento_configure_notifications 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 memento_configure_notifications. 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.
memento_configure_notifications is provided by the Memento MCP server (joyciakira/memento). 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 →