Low Risk

search_by_tag

[DEPRECATED] Search for equipment, instruments, or nodes by tag pattern. Use search_execute(query_type=

How to control search_by_tag ↓

What search_by_tag does on Engineering MCP Server

AI agents call search_by_tag to retrieve information from Engineering 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_by_tag needs a policy

This tool performs a search query to locate and retrieve data (equipment/instruments/nodes) matching a tag pattern. It is a read-only operation that returns matching results without creating, modifying, deleting, or executing any side effects. The description indicates it is also deprecated, further reducing concern.

From the tool's definition Tool name 'search_by_tag' and description explicitly state it searches for equipment, instruments, or nodes by tag pattern—a retrieval operation with no modification capability.

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

How to control search_by_tag

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

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

search_by_tag 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 Engineering 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_by_tag

What does the search_by_tag tool do? +

[DEPRECATED] Search for equipment, instruments, or nodes by tag pattern. Use search_execute(query_type=. It is categorised as a Read tool in the Engineering MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_by_tag? +

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

What risk level is search_by_tag? +

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

Can I rate-limit search_by_tag? +

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

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

search_by_tag is provided by the Engineering MCP Server MCP server (puran-water/dexpi-sfiles-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 Engineering MCP Server tool call.

Start from Engineering 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.

72 Engineering 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.