Low Risk

search_terms

Search for VFB terms using the Solr search server. Results can be filtered, excluded, or boosted by entity type using facets_annotation values. Available filter types: entity, anatomy, nervous_system, individual, has_image, adult, cell, neuron, vfb, has_neuron_connectivity, nblast, visual_system,...

Risk signalsAccepts freeform code/query input (query)

Part of the VirtualFlyBrain server.

search_terms is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE VIRTUALFLYBRAIN →

Free to start. No card required.

AI agents call search_terms to retrieve information from VirtualFlyBrain without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though search_terms only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full VirtualFlyBrain policy for all 3 tools.

Get this rule live on your own VirtualFlyBrain server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY VIRTUALFLYBRAIN →

These attack patterns abuse exactly the kind of access search_terms gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so search_terms only ever does what you allow.

SECURE VIRTUALFLYBRAIN →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the search_terms tool do? +

Search for VFB terms using the Solr search server. Results can be filtered, excluded, or boosted by entity type using facets_annotation values. Available filter types: entity, anatomy, nervous_system, individual, has_image, adult, cell, neuron, vfb, has_neuron_connectivity, nblast, visual_system, cholinergic, class, secondary_neuron, expression_pattern, gabaergic, expression_pattern_fragment, glutamatergic, feature, sensory_neuron, neuronbridge, deprecated, larva, has_region_connectivity, nblastexp, gene, primary_neuron, flycircuit, mechanosensory_system, histaminergic, lineage_mbp, peptidergic, hasscrnaseq, chemosensory_system, split, has_subclass, olfactory_system, dopaminergic, fafb, l1em, pub, enzyme, motor_neuron, cluster, lineage_6, lineage_3, serotonergic, lineage_19, lineage_cm3, lineage_dm6, proprioceptive_system, gustatory_system, sense_organ, lineage_mbp4, lineage_mbp1, lineage_1, lineage_mbp2, lineage_all1, lineage_balc, lineage_cm4, lineage_dm4, muscle, lineage_13, lineage_8, lineage_mbp3, lineage_12, lineage_dm1, lineage_dpmm1, lineage_9, lineage_cp2, lineage_dl1, fanc, lineage_7, lineage_vpnd2, lineage_dm3, lineage_dpmpm2, lineage_14, lineage_4, lineage_blp1, lineage_dalv2, lineage_eba1, lineage_dm2, lineage_dpmpm1, auditory_system, lineage_16, lineage_blvp1, lineage_blav2, lineage_vlpl2, lineage_alad1, lineage_bamv3, lineage_bld6, lineage_vpnd1, synaptic_neuropil, lineage_23, lineage_17, lineage_10, lineage_dplpv, lineage_21, lineage_alv1 Multiple filter_types are ANDed (results must match ALL). Multiple exclude_types are ORed (any match excludes). boost_types soft-rank matching results higher without excluding others.. It is categorised as a Read tool in the VirtualFlyBrain MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_terms? +

Register the VirtualFlyBrain 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 VirtualFlyBrain. 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 VirtualFlyBrain MCP server (https://vfb3-mcp.virtualflybrain.org). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every VirtualFlyBrain tool call.

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

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.