Low Risk

search_items

Search for items in Things.

How to control search_items ↓

AI agents call search_items 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.

Low Risk

The search_items tool retrieves or queries existing items from the Things 3 task management system without creating, modifying, or deleting data. It is a read-only operation that has no side effects beyond returning search results. The blast radius of misuse is minimal—an AI agent could only over-search or consume API quota, not cause data loss or financial harm.

From the tool's definition Tool name 'search_items' and description 'Search for items in Things' indicate a query/retrieval operation with no modification or deletion of data.

Documented attack patterns abuse exactly the kind of access search_items 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_items:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_items": {}
  }
}

search_items is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Things 3 MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the search_items tool do? +

Search for items in Things. It is categorised as a Read tool in the Things 3 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_items? +

Register the Things 3 MCP Server MCP server in PolicyLayer and add a rule for search_items: 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.

What risk level is search_items? +

search_items is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_items? +

Yes. Add a rate_limit block to the search_items 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.

How do I block search_items completely? +

Set action: deny in the PolicyLayer policy for search_items. 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.

What MCP server provides search_items? +

search_items 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.

Enforce policy on every Things 3 MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.