Initializes a professional 'tasks' table in the specified database.
AI agents use init_todo_schema to create or update resources in Pg Mnemosyne — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pg Mnemosyne environment.
Creating a table schema is a Write operation: it modifies the database structure but is reversible (the table can be dropped). It does not execute arbitrary code, delete data, or cause financial impact. The action is predictable and scoped to schema initialization rather than data manipulation.
From the tool's definition Tool name 'init_todo_schema' and description 'Initializes a professional tasks table in the specified database' indicate table creation—a reversible data structure modification.
Attacks that exploit this kind of access
Initializes a professional 'tasks' table in the specified database. It is categorised as a Write tool in the Pg Mnemosyne MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pg Mnemosyne MCP server in PolicyLayer and add a rule for init_todo_schema: 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 Pg Mnemosyne. Nothing to install.
init_todo_schema 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 init_todo_schema 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 init_todo_schema. 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.
init_todo_schema is provided by the Pg Mnemosyne MCP server (janadasroor/pg-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 →