AI agents use set_whether_to_annonimize to create or update resources in Memory-Plus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memory-Plus environment.
The tool modifies system state (anonymization setting) rather than retrieving data, placing it in Write rather than Read. It is not Destructive (reversible), not Execute (not running arbitrary code), and not Financial. However, confidence is lowered from ideal due to the empty description and potential typo in the tool name, which creates minor ambiguity about its exact scope and effects.
From the tool's definition Tool name 'set_whether_to_annonimize' (likely 'anonymize') suggests modifying a configuration or metadata flag that controls how memories are stored or displayed.
Documented attack patterns abuse exactly the kind of access set_whether_to_annonimize gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memory-Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for set_whether_to_annonimize:
{
"version": "1",
"default": "deny",
"tools": {
"set_whether_to_annonimize": {
"limits": [
{
"counter": "set_whether_to_annonimize_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_whether_to_annonimize stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
set_whether_to_annonimize. It is categorised as a Write tool in the Memory-Plus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memory-Plus MCP server in PolicyLayer and add a rule for set_whether_to_annonimize: 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 Memory-Plus. Nothing to install.
set_whether_to_annonimize 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_whether_to_annonimize 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_whether_to_annonimize. 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_whether_to_annonimize is provided by the Memory-Plus MCP server (yuchen20/memory-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Memory-Plus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Memory-Plus tools catalogued and risk-classified — across an index of 42,500+ MCP servers.