Add a new item to the inbox with timestamp
AI agents use inbox_add to create or update resources in Mcp Obsidian Planner — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Obsidian Planner environment.
This tool creates or modifies data reversibly by adding a new inbox item. It does not retrieve data (Read), execute arbitrary code or commands (Execute), permanently delete data (Destructive), or involve financial transactions (Financial). The impact is localized to a single inbox entry with minimal blast radius if misused by an agent—worst case, unwanted items are added to the inbox and can be manually removed.
From the tool's definition Tool name 'inbox_add' and description 'Add a new item to the inbox with timestamp' indicate creation of new data in the inbox.
Attacks that exploit this kind of access
Add a new item to the inbox with timestamp. It is categorised as a Write tool in the Mcp Obsidian Planner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Obsidian Planner MCP server in PolicyLayer and add a rule for inbox_add: 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 Mcp Obsidian Planner. Nothing to install.
inbox_add 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 inbox_add 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 inbox_add. 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.
inbox_add is provided by the Mcp Obsidian Planner MCP server (jarero321/mcp-obsidian-planner). 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 →