obsidian_write
AI agents use obsidian_write to create or update resources in PM-MCP (Portfolio Management MCP Server) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PM-MCP (Portfolio Management MCP Server) environment.
Based on the name alone, this appears to be a Write operation that creates or modifies data (notes in Obsidian) reversibly. Without a description, confidence is moderate but not low because the name is clear.
From the tool's definition Tool named 'obsidian_write' with no description provided. The name indicates a write operation to Obsidian (a note-taking/knowledge management system). The 'write' verb combined with integration context suggests creating or modifying documents/notes.
Attacks that exploit this kind of access
obsidian_write. It is categorised as a Write tool in the PM-MCP (Portfolio Management MCP Server) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PM-MCP (Portfolio Management MCP Server) MCP server in PolicyLayer and add a rule for obsidian_write: 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 PM-MCP (Portfolio Management MCP Server). Nothing to install.
obsidian_write 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 obsidian_write 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 obsidian_write. 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.
obsidian_write is provided by the PM-MCP (Portfolio Management MCP Server) MCP server (surplus96/pm-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 →