adjust_memento_confidence
AI agents use adjust_memento_confidence 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.
Based on the tool name and sibling context, this tool modifies confidence values associated with mementos in the knowledge base. This is a reversible write operation (confidence can be adjusted up or down). The description is empty, which lowers confidence. Severity is medium because misuse could corrupt the AI assistant's long-term memory reliability/trustworthiness of stored knowledge.
From the tool's definition Tool name: adjust_memento_confidence; description is empty. Sibling tools include 'boost_memento_confidence' and 'apply_memento_confidence_decay', suggesting confidence adjustment is a reversible modification of a memento's metadata.
Attacks that exploit this kind of access
adjust_memento_confidence. 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 adjust_memento_confidence: 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.
adjust_memento_confidence 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 adjust_memento_confidence 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 adjust_memento_confidence. 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.
adjust_memento_confidence 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 →