set_memento_decay_factor
AI agents use set_memento_decay_factor to create or update resources in MCP Memento — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Memento environment.
The tool modifies memento system parameters (decay factor) which affects how confidence scores degrade over time. This is a Write operation—it changes system state reversibly. Severity is medium because misconfiguration could degrade the quality of recalled information for the AI agent, but the change can be reverted.
From the tool's definition Tool name 'set_memento_decay_factor' combined with server context showing 'intelligent confidence tracking' and sibling tool 'apply_memento_confidence_decay' indicates this tool modifies decay parameters affecting stored mementos.
Attacks that exploit this kind of access
set_memento_decay_factor. It is categorised as a Write tool in the MCP Memento MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Memento MCP server in PolicyLayer and add a rule for set_memento_decay_factor: 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 MCP Memento. Nothing to install.
set_memento_decay_factor 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 set_memento_decay_factor 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 set_memento_decay_factor. 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.
set_memento_decay_factor is provided by the MCP Memento MCP server (x-hannibal/mcp-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 →