AI agents call search_advanced to retrieve information from Things 3 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
'search_advanced' most naturally fits the Read category as a query/search operation on existing tasks and projects. The pattern of sibling tools being getters and the absence of any language suggesting modification, deletion, or execution supports this classification. Low severity due to read-only nature with minimal blast radius.
From the tool's definition Tool name 'search_advanced' and context within Things 3 task management server suggest data retrieval. Sibling tools include multiple 'get_*' operations (get_anytime, get_areas, get_inbox, get_logbook, get_projects, get_random_anytime, get_random_inbox,…
Documented attack patterns abuse exactly the kind of access search_advanced gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Things 3 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_advanced:
{
"version": "1",
"default": "deny",
"tools": {
"search_advanced": {}
}
}search_advanced is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_advanced. It is categorised as a Read tool in the Things 3 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Things 3 MCP Server MCP server in PolicyLayer and add a rule for search_advanced: 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 Things 3 MCP Server. Nothing to install.
search_advanced 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 search_advanced 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 search_advanced. 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.
search_advanced is provided by the Things 3 MCP Server MCP server (rossshannon/things3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 Things 3 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 Things 3 MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.