AI agents invoke memento_toggle_precognition 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.
Toggling a background daemon is an Execute-category action: it starts or stops an autonomous background process. The [DEPRECATED] tag and vague description reduce confidence, but starting/stopping daemons can have broad side effects on system behavior. Severity is medium given the blast radius of enabling/disabling autonomous background intelligence in an AI memory middleware.
From the tool's definition 'Toggle the Pre-cognitive Intervention background daemon' — enables or disables a background daemon process
Attacks that exploit this kind of access
[DEPRECATED] Toggle the Pre-cognitive Intervention background daemon. 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_toggle_precognition: 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_toggle_precognition 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_toggle_precognition 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_toggle_precognition. 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_toggle_precognition 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 →