Initialize a new project with playbook and optional repository integration
AI agents use init_project to create or update resources in Obsidian Ai Curator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Ai Curator environment.
Initializing a project creates new files/structures (playbook and potentially repository integration), which is a Write operation. It may also trigger external integrations (repository), but the primary action is creating/setting up project artifacts. No indication of destructive or financial operations. Confidence is moderate because the description is vague about the full scope of what 'initialize' entails.
From the tool's definition Initialize a new project with playbook and optional repository integration
Documented attack patterns abuse exactly the kind of access init_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Ai Curator, and nothing reaches the server without passing your rules. This is the rule we recommend for init_project:
{
"version": "1",
"default": "deny",
"tools": {
"init_project": {
"limits": [
{
"counter": "init_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}init_project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Initialize a new project with playbook and optional repository integration. It is categorised as a Write tool in the Obsidian Ai Curator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Ai Curator MCP server in PolicyLayer and add a rule for init_project: 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 Obsidian Ai Curator. Nothing to install.
init_project 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_project 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_project. 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_project is provided by the Obsidian Ai Curator MCP server (nwant/obsidian-ai-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Ai Curator, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 Obsidian Ai Curator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.