Low Risk

search_terms

search_terms

How to control search_terms ↓

What search_terms does on OLS MCP Server

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

Low Risk

Why search_terms needs a policy

The tool retrieves or queries ontology terms without modifying, deleting, or executing external operations. It fits the Read category as a search/retrieval function. Severity is low because misuse results only in unwanted data queries against a public knowledge base, with no blast radius for data modification or system compromise.

From the tool's definition Tool is named 'search_terms' and is part of a server that 'search[es] and retrieve[s] terms from biological and medical ontologies'.

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

How to control search_terms

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

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

search_terms 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 OLS 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.

Related tools and policies

Go deeper

Questions about search_terms

What does the search_terms tool do? +

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

How do I enforce a policy on search_terms? +

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

What risk level is search_terms? +

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

Can I rate-limit search_terms? +

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

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

search_terms is provided by the OLS MCP Server MCP server (seandavi/ols-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OLS MCP Server tool call.

Start from OLS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

7 OLS MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.