Manage context memory instances with personality-driven chat capabilities
AI agents use context-manage to create or update resources in MCP LLM Generator v2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP LLM Generator v2 environment.
This tool creates or modifies context memory instances, which are data structures stored for conversation state. While not destructive (data can be updated/overwritten reversibly) and not executing arbitrary code directly, it writes/modifies application state.
From the tool's definition Tool name contains 'manage' which implies modification; description states 'Manage context memory instances' indicating creation/modification of stored context data. The phrase 'personality-driven chat capabilities' suggests persistent state changes.
Attacks that exploit this kind of access
Manage context memory instances with personality-driven chat capabilities. It is categorised as a Write tool in the MCP LLM Generator v2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP LLM Generator v2 MCP server in PolicyLayer and add a rule for context-manage: 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 LLM Generator v2. Nothing to install.
context-manage 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 context-manage 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 context-manage. 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.
context-manage is provided by the MCP LLM Generator v2 MCP server (mako10k/mcp-llm-generator). 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 →