Low Risk

search_entities

search_entities

How to control search_entities ↓

AI agents call search_entities to retrieve information from Forgetful without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Search operations are read-only and retrieve data without side effects. The empty description prevents higher confidence but the name 'search_entities' combined with the server's documented retrieval capability clearly indicates a Read function. No data is created, modified, deleted, executed, or subject to financial impact.

From the tool's definition Tool name 'search_entities' indicates a query/search operation on stored entities. Given the server's stated purpose of 'storage and retrieval' with 'semantic search', this tool performs retrieval without modification.

Documented attack patterns abuse exactly the kind of access search_entities gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Forgetful, and nothing reaches the server without passing your rules. This is the rule we recommend for search_entities:

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

search_entities 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 Forgetful — 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_entities tool do? +

search_entities. It is categorised as a Read tool in the Forgetful MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_entities? +

Register the Forgetful MCP server in PolicyLayer and add a rule for search_entities: 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 Forgetful. Nothing to install.

What risk level is search_entities? +

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

Can I rate-limit search_entities? +

Yes. Add a rate_limit block to the search_entities 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_entities completely? +

Set action: deny in the PolicyLayer policy for search_entities. 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_entities? +

search_entities is provided by the Forgetful MCP server (scottrbk/forgetful). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Forgetful tool call.

Deterministic rules across all 59 Forgetful tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

59 Forgetful 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.