// MCP TOOL REFERENCE

general_api_request

Execute arbitrary HTTP API requests to Elasticsearch

Can run any API call against the cluster

Part of the Elasticsearch MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

elasticsearch-mcp-server Execute Risk 5/5

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke general_api_request to trigger processes or run actions in Elasticsearch. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON GENERAL_API_REQUEST

general_api_request can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-cr7258-elasticsearch-mcp-server.yaml

tools:
  general_api_request:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Elasticsearch policy for all 20 tools.

// DETAILS

Tool Name general_api_request

Category Execute

MCP Server Elasticsearch MCP Server

Risk Level High

// MORE ELASTICSEARCH TOOLS

Destructive delete_alias Destructive delete_by_query Destructive delete_data_stream Destructive delete_document Destructive delete_index Write create_data_stream Write create_index Write index_document

View all 20 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like general_api_request have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Agent Passport System — Cryptographic Identity for AI Agents commerce_preflight Agent Passport System — Cryptographic Identity for AI Agents execute_with_context Agent Passport System — Cryptographic Identity for AI Agents gateway_execute_approval Agent Passport System — Cryptographic Identity for AI Agents governance_360 Agent Passport System — Cryptographic Identity for AI Agents parse_governance_block_html AgentClear — API Marketplace for AI Agents call_service

// IN CONTEXT OF HIGH RISK

general_api_request is one of the high-risk operations in Elasticsearch. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the general_api_request tool do? +

Execute arbitrary HTTP API requests to Elasticsearch. It is categorised as a Execute tool in the Elasticsearch MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on general_api_request? +

Add a rule in your Intercept YAML policy under the tools section for general_api_request. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Elasticsearch MCP server.

What risk level is general_api_request? +

general_api_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit general_api_request? +

Yes. Add a rate_limit block to the general_api_request rule in your Intercept 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 general_api_request completely? +

Set action: deny in the Intercept policy for general_api_request. 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 general_api_request? +

general_api_request is provided by the Elasticsearch MCP server (elasticsearch-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

general_api_request

Enforce policies on Elasticsearch