AI agents use litopys_create to create or update resources in Litopys — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Litopys environment.
This tool creates new data structures (nodes) in the graph-based memory system. It is reversible via deletion and has bounded blast radius (creates only what the agent specifies), making it Write rather than Destructive or Execute. The medium severity reflects that uncontrolled node creation could degrade system performance or pollute the knowledge graph, but individual creations are not catastrophic.
From the tool's definition Tool description states 'Create a new node in the knowledge graph', which is a CREATE operation that modifies data by adding new nodes.
Attacks that exploit this kind of access
Create a new node in the knowledge graph. Fails if the id already exists. It is categorised as a Write tool in the Litopys MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Litopys MCP server in PolicyLayer and add a rule for litopys_create: 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 Litopys. Nothing to install.
litopys_create 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 litopys_create 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 litopys_create. 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.
litopys_create is provided by the Litopys MCP server (litopys-dev/litopys). 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 →