search_execute

THE RISK

Low Risk

Why search_execute needs a policy

Search operations retrieve and query data without modifying, deleting, or executing external code. Despite the word 'execute' in the name, the context ('consolidates all search_* operations') clarifies this is a search/query aggregator, not a code execution tool. It poses minimal risk as a read-only operation within the engineering diagram domain.

From the tool's definition Tool name contains 'search_execute' described as 'Unified search tool - consolidates all search_* operations'. The description explicitly indicates this performs search operations, which are read-only queries.

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

POLICY

How to control search_execute

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_execute:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_execute": {}
  }
}

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

Create a free account and register Engineering MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Engineering MCP Server tools

Destructive layout_delete Delete a layout from the store Execute layout_compute Compute layout for a model using ELK. Produces orthogonal edge routing suitable for P&ID d Execute model_batch_apply Execute multiple operations in a single call for efficiency Execute rules_apply Apply validation rules and return structured issues for LLM processing. Optionally auto-fi Write area_deploy Deploy a template into a model (STRATEGIC operation - replaces 50+ atomic calls) Write model_tx_begin Start a transaction on a model for atomic multi-operation changes Write model_combine Merge multiple DEXPI models into one combined model. Combines all tagged plant items, inst Write model_load Import a model from various formats (JSON, Proteus XML, SFILES string) - Replaces dexpi_im

All 72 Engineering MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search_execute

What does the search_execute tool do? +

Unified search tool - consolidates all search_* operations. 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_execute? +

Register the Engineering MCP Server MCP server in PolicyLayer and add a rule for search_execute: 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_execute? +

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

Can I rate-limit search_execute? +

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

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

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

CHECK YOUR STACK →