context_bundle
AI agents call context_bundle to retrieve information from Mnemosyne MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without explicit documentation, the name 'context_bundle' most likely refers to assembling or retrieving contextual information from the knowledge graph—a read-like operation. The empty description reduces confidence, but the suffix pattern and context among other tools suggests no write, destructive, or execution capabilities. Conservative classification as Read with lower confidence due to insufficient detail.
From the tool's definition Tool name 'context_bundle' suggests data retrieval or aggregation; description is empty, limiting certainty.
Attacks that exploit this kind of access
context_bundle. It is categorised as a Read tool in the Mnemosyne MCP MCP Server, which means it retrieves data without modifying state.
Register the Mnemosyne MCP server in PolicyLayer and add a rule for context_bundle: 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 Mnemosyne MCP. Nothing to install.
context_bundle is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the context_bundle 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_bundle. 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_bundle is provided by the Mnemosyne MCP server (sophia-labs/mnemosyne-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 →