AI agents invoke memento_coercion to trigger actions in Memento. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The term 'Active Coercion' combined with an 'apply_preset' action implies this tool executes behavioral enforcement rules or constraints on the AI agent's operation. This goes beyond mere data reads or writes — it triggers external operational effects by enforcing coercion presets.
From the tool's definition 'Active Coercion management' and actions including 'apply_preset' — applying coercion rules triggers autonomous enforcement behavior in the AI agent
Attacks that exploit this kind of access
Active Coercion management. Actions: list_presets, apply_preset,. It is categorised as a Execute tool in the Memento MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Memento MCP server in PolicyLayer and add a rule for memento_coercion: 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_coercion is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the memento_coercion 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_coercion. 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_coercion 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 →