Store a memory (decision, solution, pattern, architecture note, or general note) with semantic search capability
AI agents use doclea_store to create or update resources in Doclea MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doclea MCP environment.
This tool writes new entries to a persistent memory store. It creates data reversibly (a sibling 'doclea_delete' tool exists, implying stored items can be removed). Misuse could pollute the memory store with incorrect architectural decisions or patterns, misleading AI coding assistants, giving it medium severity.
From the tool's definition 'Store a memory' — creates or persists new data (decisions, solutions, patterns, architecture notes) with semantic search capability
Attacks that exploit this kind of access
Store a memory (decision, solution, pattern, architecture note, or general note) with semantic search capability. It is categorised as a Write tool in the Doclea MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Doclea MCP server in PolicyLayer and add a rule for doclea_store: 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 Doclea MCP. Nothing to install.
doclea_store 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 doclea_store 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 doclea_store. 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.
doclea_store is provided by the Doclea MCP server (quanticstudios/doclea-mcp). 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 →