edit_block_text
AI agents use edit_block_text to create or update resources in Mnemosyne MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mnemosyne MCP environment.
The verb 'edit' combined with 'text' in a knowledge graph management system indicates data modification rather than destruction or execution of arbitrary operations. This is a Write operation because edits are typically reversible. Medium severity reflects that modifying knowledge graph blocks could affect dependent queries or operations, but the impact is constrained to text blocks rather than entire records.
From the tool's definition Tool name 'edit_block_text' indicates modification of text blocks; no description provided to confirm scope or reversibility. Context from sibling tools (create_graph, create_wires, delete) suggests this server manages knowledge graph data structures.
Attacks that exploit this kind of access
edit_block_text. It is categorised as a Write tool in the Mnemosyne MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mnemosyne MCP server in PolicyLayer and add a rule for edit_block_text: 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.
edit_block_text 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 edit_block_text 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 edit_block_text. 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.
edit_block_text 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 →