Search using JsonLogic query. Supports glob and regexp operators for pattern matching.
AI agents call complex_search to retrieve information from Obsidian Modified without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries data within Obsidian notes using a structured logic system and pattern matching. It returns search results without creating, modifying, or deleting content. No side effects are mentioned or implied. The use of JsonLogic, glob, and regexp are all read-only pattern matching mechanisms.
From the tool's definition Tool name 'complex_search' combined with description 'Search using JsonLogic query. Supports glob and regexp operators for pattern matching' indicates data retrieval via query patterns, with no mention of modification, deletion, or command execution…
Attacks that exploit this kind of access
Search using JsonLogic query. Supports glob and regexp operators for pattern matching. It is categorised as a Read tool in the Obsidian Modified MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Modified MCP server in PolicyLayer and add a rule for complex_search: 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 Modified. Nothing to install.
complex_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the complex_search 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 complex_search. 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.
complex_search is provided by the Obsidian Modified MCP server (@marwansaab/obsidian-modified-mcp-server). 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 →