AI agents invoke memento_check_goal_alignment 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 tool runs submitted code or plans through an enforcement/evaluation pipeline, which constitutes executing an external operation whose effects depend on arguments. While it may be read-like in intent (checking alignment), enforcement implies side effects such as blocking, modifying, or flagging actions. The DEPRECATED status and vague description lower confidence.
From the tool's definition 'Submit code or plans to be strictly evaluated' and 'Level 2 Enforcer' — implies active evaluation/enforcement logic is triggered against project goals
Attacks that exploit this kind of access
[DEPRECATED] Level 2 Enforcer: Submit code or plans to be strictly evaluated against the project. 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_check_goal_alignment: 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_check_goal_alignment 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_check_goal_alignment 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_check_goal_alignment. 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_check_goal_alignment 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 →