AI agents use create_knowledge_record to create or update resources in Todos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.
This tool creates new records in a local database (SQLite), which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because misuse could pollute the knowledge base with incorrect information, but the impact is confined to local project state and is reversible through updates or deletions.
From the tool's definition Tool description states 'Create a local project knowledge record' — the verb 'Create' and action of storing 'decisions, architecture notes, tradeoffs, or task-linked context' in 'local SQLite state' indicates data creation and modification.
Attacks that exploit this kind of access
Create a local project knowledge record for decisions, architecture notes, tradeoffs, or task-linked context. Uses only local SQLite state. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todos MCP server in PolicyLayer and add a rule for create_knowledge_record: 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 Todos. Nothing to install.
create_knowledge_record 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 create_knowledge_record 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 create_knowledge_record. 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.
create_knowledge_record is provided by the Todos MCP server (@hasna/todos). 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 →