Write or update a Claude Code project memory file (.md). Persists project context, user preferences, feedback, and reference notes across Claude Code sessions. Filename must end in .md with lowercase alphanumeric characters. Path traversal is blocked. Requires authentication.Use this to persist p...
Risk signalsAccepts file system path (filename) · Accepts raw HTML/template content (content)
Part of the ThinkNEO Control Plane server.
Free to start. No card required.
AI agents use thinkneo_write_memory to create or modify resources in ThinkNEO Control Plane. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call thinkneo_write_memory repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach ThinkNEO Control Plane.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"thinkneo_write_memory": {
"limits": [
{
"counter": "thinkneo_write_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full ThinkNEO Control Plane policy for all 68 tools.
These attack patterns abuse exactly the kind of access thinkneo_write_memory gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Write or update a Claude Code project memory file (.md). Persists project context, user preferences, feedback, and reference notes across Claude Code sessions. Filename must end in .md with lowercase alphanumeric characters. Path traversal is blocked. Requires authentication.Use this to persist project context, user preferences, feedback, and reference notes across Claude Code sessions. The filename must end in .md and contain only lowercase letters, digits, underscores, and hyphens (e.g. 'user_fabio.md', 'project_new_feature.md'). Path traversal is blocked.. It is categorised as a Write tool in the ThinkNEO Control Plane MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ThinkNEO Control Plane MCP server in PolicyLayer and add a rule for thinkneo_write_memory: 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 ThinkNEO Control Plane. Nothing to install.
thinkneo_write_memory 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 thinkneo_write_memory 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 thinkneo_write_memory. 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.
thinkneo_write_memory is provided by the ThinkNEO Control Plane MCP server (https://mcp.thinkneo.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 68 ThinkNEO Control Plane tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.